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

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

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-05-07 21:37:29 CEST

On Fri, 2004-05-07 at 13:41, Daniel F. Savarese wrote:

> 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.

This experiment is a red herring. Two svn clients cannot 'svn up' or
'svn commit' in the same working copy directory at the same time,
period. That's *exactly* the reason the client locks working copy
directories when operating on them. It's a deliberate design.

So the "lock" error you're seeing has nothing to do with svn-commit.tmp
filename clashes.

The only reason 'svn commit' resorts to generating unique tmpfile names
is the off-chance that an old commit-log file has been left behind by a
previous failed commit. We don't want to accidentally clobber it.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 8 01:17:53 2004

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.