On 7/7/06, Gavin Lambert <gavinl@compacsort.com> wrote:
> Repost, since the first one seemed to get eaten (apologies if you did
> actually get it):
>
> > Imagine this folder layout:
> > trunk/folder1/
> > trunk/folder1/fileA
> > trunk/folder2/
> >
> > Now I decide to do a bit of rearranging (as part of a larger edit)
> > and want to move it over to a different folder:
> > > svn mv trunk/folder1/fileA trunk/folder2/
> >
> > That's ok, and leaves fileA in an 'add with history' state.
> >
> > After some more development (without committing from the move,
> > because things are still not in a good commit state), I decide that
> > it's a good idea to rename fileA to fileB, since its function has
> > changed.
> >
> > > svn mv trunk/folder2/fileA trunk/folder2/fileB
> > svn: Use --force to override this restriction
> > svn: Move will not be attempted unless forced
> > svn: 'fileA' has local modifications
> >
> > This is odd behaviour, since a move/rename should be nondestructive
> > in this context. Still:
> >
> > > svn mv --force trunk/folder2/fileA trunk/folder2/fileB
> > svn: Cannot copy or move 'findsym.c': it's not in the repository
> > yet; try committing first
> >
> > This is just plain wrong. Don't force me to commit when I don't want
> > to.
There is actually already some work being done on this. Paul Burba
has some work in progress patches to make it possible.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 7 16:34:50 2006