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

Re: mixed revision working copy -- rationale?

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-05-17 18:25:27 CEST

On May 17, 2005, at 10:38 AM, Bob Proulx wrote:

> At the time of
> the commit your working copy must be up to date with the repository


Suppose the repository is at r10.

Suppose you have a working copy with two sibling files, 'foo' and 'bar'.

Now you commit you change to 'foo', and the commit succeeds,
informing you that you've just created r20.

r20? How is that? Well, apparently other people have been making
changes too.

If, immediately after the commit, the svn client were to simply mark
your entire working copy as being at r20, it would be a complete
lie. It would claim that the parent directory of foo and bar is r20,
but how does it actually know that? "r20 of parent-directory" has a
very specific definition: it has a specific set of children, and a
specific set of properties.

What if somewhere between r12 and r20, another user attached new
directory-properties to the parent directory? What if files were
removed from the directory? What if new files were added?

There's no way that your svn client knows that you have r20 of the
parent directory. The only safe assumption is that you still have
r12 of the parent directory, r12 of 'bar', and r20 of 'foo'.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 17 18:28:10 2005

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.