My app relied on the security vulnerability fixed in Rails 3.0.1.
While I did specify attributes such as name and email, my main goal
was to use an existing record by specifying the id. The 3.0.1 patch
does not make it possible to specify id in nested attributes. It now
raises a raise_nested_attrib
On Tue, Oct 12, 2010 at 2:46 PM, Luke Chadwick
wrote:
> Hi All,
> I updated
> https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2350-logtailer-ignores-configlog_path
> a while back with a suggestion for how to create a patch for the
> problem, and wanted to get someone to +1 t
I strongly disagreed with hemant. i recently just got a patch in without
using any twitter DM, personal email or the guarded campfire chat room.
If you are serious about your patch, try to ask rubyist around you to check
out your patch and comment about it on the Lighthouse ticket. Remember,
Rails
Core team members have lives too.
If you'd like a patch reviewed then send me an email at radarliste...@gmail.com
and I will review it if the core team will not.
On 16/10/2010, at 6:16, hemant wrote:
> On Tue, Oct 12, 2010 at 2:46 PM, Luke Chadwick
> wrote:
>> Hi All,
>> I updated
>> htt
me as well: siong1...@gmail.com.
On Fri, Oct 15, 2010 at 5:53 PM, Ryan Bigg wrote:
> Core team members have lives too.
>
> If you'd like a patch reviewed then send me an email at
> radarliste...@gmail.com and I will review it if the core team will not.
>
>
>
> On 16/10/2010, at 6:16, hemant wro
