"Ivan Zhakov" <email@example.com> wrote on 04/16/2006 03:57:49 PM:
> > 1) Improve Copy/Move support.
> > This is not about "true renames" although I suspect having them could
> > I come to Subversion from a Java persepective and Java programmers are
> > always interested in Subversion because it handles move/rename better
> > CVS. Since refactoring is such a hot topic in Java programming,
> > think switching to Subversion from CVS will bring them a lot of
> > In reality, that is not always the case, because people often like to
> > several refactorings before doing a commit. For example, a folder
> > containing classes might be renamed, then some of the classes in that
> > might also be renamed, and/or moved to other folders. I do not know
> > the scenarios where Subversion has problems, but it definitely has
> > This comes up a lot with Subclipse users as they get errors when we
> > move something and Subversion does not let them because it has already
> > moved.
> > JavaSVN has already implemented what they call a "Smart Move" feature
> > gets around these problems by updating the WC as necessary. Perhaps
> > could document how they handle various scenarios to see if the design
> > work for Subversion.
> I've already posted patch to enable moving moved files. But there was
> objections on idea itself. See discussion here:
Is there any chance this could get revived? It didn't seem the objections
were that strong, I thought they were seeking more work or clarification.
It would stink to discard a useful feature over theoretical disputes. One
thing that occurs to me is what if we initially limited the scope of the
patch to the move subcommand? Refactoring almost exclusively uses
move/rename and there really isn't any ambiguity that I can see to
supporting letting a file or folder be moved multiple times.
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Apr 17 15:10:17 2006