Jerry Haltom wrote:
> Off the wall idea. Basically it's saying "is this file the results of
> that file?" This could be determined by comparing all the new files
> against all the existing files looking for differences of a certain
> threshold. Exactly the same? It's an obvious the copy. 99 out of 100
> lines the same? Probably a copy.
Would be very slow... And I don't think it is a good idea to scan all
files around there. What if you do a `mv foo bar/foo`?
> Regardless of all that. Being able to run "svn mv" to register a move
> that has already happened would be totally useful. Perhaps a command
> line option.
>
> $ mv foo.txt bar.txt
> $ svn mv foo.txt bar.txt
> svn: Path 'foo.txt' does not exist
Hm, maybe a svn mv --force to tell subversion "take this file from now on".
> And then another idea just occurred to me which sounds kind of fun, and
> I might want to work on it for giggles. A "working copy daemon", that
> runs against a working copy and monitors the kernel file event
> notification mechanism and makes the appropriate svn modifications.
I don't think this would run on all platforms. I don't like to have a
different workflow on another platform. You always would have to check
if the daemon is running before you start working so you would end up in
`svn mv` again.
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 26 18:43:06 2005