Yes. Please follow the below steps to reproduce the behavior. Do you think
it is bug or am I missing something?
Thanks,
Vinay
/indreshv/duplicate> svn checkout file:///indreshv/test/trunk/src/java java1
A java1/a.java
A java1/b.java
A java1/c.java
A java1/d.java
A java1/new.java
Checked out revision 153.
/indreshv/duplicate> svn checkout file:///indreshv/test/trunk/src/java java2
A java2/a.java
A java2/b.java
A java2/c.java
A java2/d.java
A java2/new.java
Checked out revision 153.
/indreshv/duplicate> cd java1
/indreshv/duplicate/java1> ls
a.java b.java c.java d.java new.java
/indreshv/duplicate/java1> svn delete new.java
D new.java
indreshv_at_invest1:/u/indreshv/duplicate/java1> svn commit -m "deleting
new.java" .
Deleting new.java
Committed revision 154.
/indreshv/duplicate> cd java2
/indreshv/duplicate/java2> ls
a.java b.java c.java d.java new.java
/indreshv/duplicate/java2> svn delete new.java
D new.java
/indreshv/duplicate/java2> svn commit -m "deleting new.java again" .
Deleting new.java
Committed revision 155.
/indreshv/duplicate/java2> svn log file:///indreshv/test -v -r154
------------------------------------------------------------------------
r154 | indreshv | 2009-02-16 13:29:18 +0530 (Mon, 16 Feb 2009) | 1 line
Changed paths:
* D /trunk/src/java/new.java*
deleting new.java
------------------------------------------------------------------------
/indreshv/duplicate/java2> svn log file:///indreshv/test -v -r155
------------------------------------------------------------------------
r155 | indreshv | 2009-02-16 13:29:58 +0530 (Mon, 16 Feb 2009) | 1 line
Changed paths:
deleting new.java again
------------------------------------------------------------------------
On Sat, Feb 14, 2009 at 5:46 AM, Ryan Schmidt <
subversion-2009a_at_ryandesign.com> wrote:
> On Feb 10, 2009, at 12:49, vinay i wrote:
>
> Probably many of you would be aware of this. Assume I have a older
>> checked out copy and another developer did a "svn delete" and "svn
>> commit" on a particular file in his checked out copy of the same
>> repository. Now, if I perform "svn delete" and "svn commit" on the
>> same file without doing "svn update" it still allows me to commit.
>> This is something which we don't expect to happen. Is there any
>> standard procedure to avoid such commits?
>>
>
> I wouldn't have expected that. Do you have a reproduction recipe we can
> try?
>
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1169428
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-16 09:41:50 CET