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

Re: Is this a peg revision bug?

From: Malcolm Rowe <malcolm-svn-dev_at_farside.org.uk>
Date: 2007-04-04 23:12:12 CEST

On Wed, Apr 04, 2007 at 10:04:24PM +0100, Malcolm Rowe wrote:
> This is true, but it's impossible to guarantee - the commits of r4 and r6
> are racing with all other commits by any user in the repository.

It strikes me that's not very clear. What I meant is that there's no
way to atomically commit a change via a wc that copies a file from the
revision that is HEAD at the time the commit is made (as you typically
want to do if you're renaming a file).

The solution might just be to do all renames and copies via URLs, but
that's not great. A better solution would be for log-tracing to
understand that if a node doesn't change between rX and rY, we can trace
back the history from rZ to the copyfrom rX and 'forward' to rY (which
is actually the same node, I think).


  • application/pgp-signature attachment: stored
Received on Wed Apr 4 23:12:25 2007

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.