for this is not achievable for me right now. I will log a defect
for this.
Regards,
Arjen Wisse
On Tue, Mar 29, 2011 at 6:13 AM, Daniel Shahaf wrote:
>
> Arjen Wisse wrote on Mon, Mar 28, 2011 at 09:51:43 +0200:
> > Hi Daniel,
> >
> > Thanks for responding to this issue
s.org/issues/show_bug.cgi?id=3525).
It does move the lock in the working copy, but a svn update after
moving gives a tree conflict because of the lock (that is the bug I
referred to).
Sorry for the confusion.
Regards,
Arjen Wisse
Sr. Software Engineer
awi...@cordys.com
www.cordys.com
T +31 (0)34
).
You suggested "lock the moved-from path", but how do I achieve that?
Does it mean that I require to lock it in the repository only?
Wouldn't that give a 'orphan' lock (I mean a lock only existing in the
repository, not in any working copy)?
Thanks & Regards,
Arjen
#x27;/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?
Regards,
Arjen Wisse
