Paul Maier wrote on Wed, Oct 20, 2010 at 01:55:30 +0200: > [Sorry, in my previous posting I forgot to mention the svn lock command. > Here the corrected version of my posting.] > > Hi Daniel, > > I just ran into something, that might already be fixed with your r1023571, > but I think it is worth testing: > > # 1. setup "file a" as in previous postings: > echo a > a > svn add a > svn propset svn:needs-lock "*" a > svn ci -m "" > > # 2. local modification to file a: > svn lock a > echo blah >> a > > # 3. rename file a: > svn mv a b > > # 4. want to continue to edit the file (has now name b): > -> not possible, because on the "svn mv" the file turned read-only > > > May I ask you to check if this is already covered by your r1023571? >
With head of trunk, 'b' isn't read-only: 0:% echo a > a 0:% $svn add -q a 0:% $svn ps svn:needs-lock yes -q a 0:% $svn ci -qmm 0:% 0:% $svn lock -q a Subcommand 'lock' doesn't accept option '-q [--quiet]' Type 'svn help lock' for usage. zsh: exit 1 $svn lock -q a 1:% $svn lock a 'a' locked by user 'daniel'. 0:% echo blah >> a 0:% 0:% $svn mv -q a b 0:% ls -l b -rw-r--r-- 1 daniel daniel 7 2010-10-20 02:02 b 0:% Are you able to build svn yourself from source? > Thanks & Greetings > Paul >
