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
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
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 t
