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

RE: problem arising from early entry deletion

From: Sander Striker <striker_at_apache.org>
Date: 2002-03-18 16:34:18 CET

> From: sussman@collab.net [mailto:sussman@collab.net]
> Sent: 18 March 2002 03:23

Comments from the less enlightened... (me that is).

> Ben Collins <bcollins@debian.org> writes:
>>> Principle: "Lying to the server is bad." :-) We need to stop doing it;
>>> what's the best way?
>> Could we instead (in your example) mark "." as rev=10 instead of leaving
>> it as 9?
> No, because that would be a Lie too.
> We don't *know* that we have revision 10 of the directory; we merely
> created it by committing the deletion. In the general case, suppose
> our commit created revision 15. It would be a lie to say we have
> revision 15 of the directory after the commit; what if someone added
> a file to the directory in revison 12?

Can't we mark the directory as 'dirty' after the commit (of the deletion)?
We do bump the dir rev to 15 in this case, but also set the dirty marker
on it. This way we know the rev of the dir should be at rev 15, but it
needs updating to be in the state rev 15 is in.
> We are only allowed to bump working-copy directory revisions in
> updates, or when we commit a propchange to a directory.

Hmmm, committing a propchange doesn't update the directory contents
either, so how is that not a problem? Or does your wc need to be
fully up to date at commit of the propchange? Does it fail otherwise?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 18 16:30:09 2002

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