Suppose that may be the case for "my" case. But by chance lets say I did freeze_edge to current, and I had a 0.13.0 working copy. I would still need this feature.
So it appears this doesn't have immediate fruit, but it is getting ripe for implementation. Thanks for the feedback. -Nb On 4/9/06 6:13 PM, "Michael Koziarski" <[EMAIL PROTECTED]> wrote: >> Just created a ticket for: >> >> http://dev.rubyonrails.org/ticket/4673 >> >> Which outlines the option to merge/diff or patch on upgrade. >> >> Currently I see the functionality of upgrading quite tedious, especially >> with the now planned rapid release cycle. This is solely due to the fact >> that I need to create temp files and merge core files, such as >> application.rb, application_helper.rb, with the updated Rails copy. > > Why do you need to do this? rake rails:update only changes the > javascript files. > > rails . hasn't been needed since .13->.14 > >> I am proposing we look into creating a Diff/Merge/Patch option, that creates >> a file with the changes embedded so I can look at that file, tweak it if >> necessary, and patch the WC. >> >> Ideas/comments? >> >> -Nb >> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Nathaniel S. H. Brown http://nshb.net >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> >> >> >> >> >> _______________________________________________ >> Rails-core mailing list >> Rails-core@lists.rubyonrails.org >> http://lists.rubyonrails.org/mailman/listinfo/rails-core >> > > > -- > Cheers > > Koz > _______________________________________________ > Rails-core mailing list > Rails-core@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-core ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Nathaniel S. H. Brown http://nshb.net ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
