[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: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-03-18 17:49:52 CET

Ben Collins-Sussman <sussman@collab.net> writes:
> "Sander Striker" <striker@apache.org> writes:
> > 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.
> Yes indeed, this is another solution!
> In other words, if a directory is marked "dirty", then when we send
> our update state-report to the server, we enumerate *all* immediate
> children in the report, just like CVS does all the time.
> I like this solution -- it's much simpler to implement and maintain.
> Feels cleaner to me.

I like it too!

But, we'll have to transmit the dirty bit to the server somehow. That
is, if you tell the server you have directory D at revision 9, and
then tell it you have the following children of D also at revision 9,
the server won't assume that any unmentioned children are deleted --
it will assume they're also at revision 9! :-) So state reports will
need to incorporate the dirty bit, probably not too difficult (?)...

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 18 17:41:14 2002

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