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

Re: Mysterious "Transaction is out of date" error

From: <cmpilato_at_collab.net>
Date: 2002-08-06 01:53:45 CEST

Peter Davis <peter@pdavis.cx> writes:

> On Monday 05 August 2002 10:23, cmpilato@collab.net wrote:
> > > > svn add a
> > > > touch a/b
> > > > svn add a/b
> > > > svn commit -m 'add stuff'
> > > > echo zog >> a/b
> > > > svn commit -m 'extend a/b'
> >
> > Note that if right here you add 'svn up', the bug disappears. Why?
> > Because that will cause both 'a' and 'a/b' to have the same revision.
> > That, in turn, causes the commit driver to issue only a single add of
> > 'c' as a copy of 'a', which will, as before, include 'a/b'.
>
> Since 'a' (and thus 'c') is not at HEAD, shouldn't this fail like it
> does with other out-of-date-not-at-HEAD files? Or maybe that's the
> whole problem...

'a' isn't being committed. 'c' is not 'a', it is a copy of 'a'. We
don't require the copy *source* to be up-to-date ... if we did, we'd
have no use for the syntax "svn cp -r XXX source dest". And without
*that*, Subversion has no useful tags/branches. :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 6 01:56:49 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.