Re: "svn mv" after the fact??

At 12:24 PM +0200 7/1/03, P.Marek wrote:
>So I have to
>1) move the files back
>2) do a "svn mv"
>which, as I know, could be automated away with a script, but nonetheless ...
>
>How about using the special-case in which
>a) source does no longer exist and
>b) target does exist
>just doing the bookkeeping without doing the move or showing an error??

I'm not sure, but I think what you mean here is that a move is done
in the plain file system (Unix "mv" or something like that), and you
think "svn commit" should figure out which new file matches which
missing old file Is that it?

I do not understand how we could make this intuitive leap. There are
some heuristics we could apply (such as tracking the inode number),
but they're nonportable (Windows? Inodes?) and not very reliable
(some editors change the inode when saving a change). There are also
edge cases (should we ignore every file named <oldname>.save? How
about <oldname>.bak? What if the user wanted to add *.save to the
repository? How widely throughout the WC should we search for the
moved file?).

-- 
-==-
Jack Repenning
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
o: 650.228.2562
c: 408.835-8090
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org