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

Re: simultaneous commit of two working copies fails

From: <cmpilato_at_collab.net>
Date: 2002-07-03 23:05:09 CEST

Ben Collins-Sussman <sussman@collab.net> writes:

> Josef Wolf <jw@raven.inka.de> writes:
> > On Tue, Jul 02, 2002 at 04:34:30PM -0500, Ben Collins-Sussman wrote:
> > > Alexis Huxley <ahuxley@gmx.net> writes:
> > >
> > > > 'svn help commit' says I can do the following:
> > > > te35$ svn commit gvd ade
> > >
> > > In theory, your use-case might be able to work someday too; after all,
> > > your two working copies are from the same repository, and therefore
> > > the commit could still be atomic.
> >
> > Umm... Do you suggest an automatic merge on commit? Please note that
> > both files came from the same revision of the same file in the repo.
> Well, no, I wouldn't suggest that. When the svn client goes gathering
> committable items into a list, it would/should recognize that we're
> trying to commit the same item twice with different mods, and just
> bail out.

This is, indeed, what *should* be happening (at least, it did when I
was testing it during the commit system re-write). The entire
client-side commit process is now based on URLs (instead of working
copy paths). So two files on your drive that have the same repository
URL should trigger an error in the commit process if both are modified
and targets to the same commit.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 3 23:05:39 2002

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

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