But then once you commit --keep-locks the rename, you'll have to also
move the lock from /f1/foo to /f2/foo, right?
For that matter:
% svn add iota
% svn ci -mm iota
% svn mv iota kappa
% svn lock kappa
% svn ci --keep-locks -m rename ./
should also move the lock from iota to kappa. (currently it doesn't)
This seems reasonable to me. (so, +1 to filing a feature request bug)
And to answer your question: for now, lock the moved-from path.
Arjen Wisse wrote on Wed, Mar 23, 2011 at 17:27:06 +0100:
> Let's have the following folder/file structure:
> * f1
> ** test.txt
> (so the file 'test.txt' is part of folder 'f1').
> After renaming 'f1' to 'f2' (using svn rename) I get the following
> error when executing:
> >svn lock f2/test.txt
> svn: Path '/f2/test.txt' doesn't exist in HEAD revision
> Of course, it does not exist in the HEAD revision at that location,
> because the folder is renamed. So, IMO it should lock the file
> 'test.txt' in path '/f1/test.txt' in the repository as I did not
> commit my rename yet. How can I ensure locking in this case?
> Arjen Wisse
Received on 2011-03-26 02:16:39 CET