[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Bug report against SVN 1.6.13

From: Paul Maier <svn-user_at_web.de>
Date: Wed, 20 Oct 2010 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?

Thanks & Greetings
  Paul
Received on 2010-10-20 01:56:09 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.