Ok, this makes a bit more sense now for the older versions. Wasn't aware that the "rails:upgrade" was the method to upgrade these days.
So it is not expected that Rails' future upgrades will potentially overwrite any of the files existing in my WC with new versions? I can see this is already not the case with the boot/config.rb. The capability of having a diff/merge/patch tool as an option when running the rails:upgrade could be quite useful, and would lend aide to having to create a tmp file manually and running diff against the two to see what changed. -Nb On 4/10/06 7:10 AM, "David Heinemeier Hansson" <[EMAIL PROTECTED]> wrote: >> 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. > > It's highly unlikely that we're going to spend time automating > upgrades from 0.13.x. If you're still on that version, you'll have to > do it manually. And then cherish the fact that you won't have to do it > again. > -- > David Heinemeier Hansson > http://www.loudthinking.com -- Broadcasting Brain > http://www.basecamphq.com -- Online project management > http://www.backpackit.com -- Personal information manager > http://www.rubyonrails.com -- Web-application framework > _______________________________________________ > 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
