Re: http://subversion.tigris.org/issues/show_bug.cgi?id=767

In message <D7D93DB0-A03D-11D8-A2BB-00306547BD7A@latchkey.com>, Jon Scott Steve
ns writes:
>The problem with this is that if I open another terminal and want to do
>another commit in the same directory while a commit is previously in
>progress, then I'm going to get a filename clash since the name isn't
>unique.

Hi Jon,

I haven't looked at the code as you have, but since you made me curious,
I ran a test to try to reproduce the problem with the following result:

svn: Working copy '/tmp/test' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)

Using Subversion 1.0.2 I did a checkout of a module called test and then
did:
  cd test
  touch foo
  touch bar
  svn add foo
  svn add bar
In one shell window I did:
  svn ci foo
In another I did the following while the commit message file was still
being edited by the first commit:
  svn ci bar

The second commit produced the lock error.

I wasn't sure if the problem you're reporting is that svn-commit.tmp
can be concurrently edited by two different commits (something I
can't reproduce with my test) or that you can't perform two commits
concurrently because the directory is locked. Either way it sounds
like something that would be useful to resolve.

daniel

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 8 02:08:04 2004