I was just verifying whether I understood you correctly. Going down
the road of working around this issue requires quite some effort. I
have an application which uses SVN to provide versioning for my data
(and provide collaboration possibilities) which is stored in files
with folder structures. Dur
Arjen Wisse wrote on Mon, Mar 28, 2011 at 09:51:43 +0200:
> Hi Daniel,
>
> Thanks for responding to this issue.
>
> In fact what I was expecting is that when locking the file before
> move, the lock being moved to the new location in the working copy as
> well. However, that does not happen eithe
I just realized that I mentioned something that is not true:
> In fact what I was expecting is that when locking the file before
> move, the lock being moved to the new location in the working copy as
> well. However, that does not happen either (see defect
> http://subversion.tigris.org/issues/sho
Hi Daniel,
Thanks for responding to this issue.
In fact what I was expecting is that when locking the file before
move, the lock being moved to the new location in the working copy as
well. However, that does not happen either (see defect
http://subversion.tigris.org/issues/show_bug.cgi?id=3525).
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 i
Hi,
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 cour
