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

Re: Obliterate and auditability

From: Branko Čibej <brane_at_xbc.nu>
Date: Sun, 20 Apr 2008 23:40:05 +0200

Karl Fogel wrote:
> Branko Čibej <brane_at_xbc.nu> writes:
>> Frankly, ugh, yuck. This means you have to go outside the repository
>> to get the complete history of what happened to the repository. That's
>> somewhat ... not quite there. I'd much rather have such audit info
>> recorded in carefully selected revprops, for want of a better place;
>> and yes I'm aware of the can of worms. :)
> I'm fine with that, I just don't know how to handle the case where the
> obliteration is *of* a revision.

Yes, that's the can of worms I was talking about. But there aren't that
many options; we either keep an empty revision (i.e., no changes, just
the elision record); but IIRC that causes all sorts of other problems;
or, we put the elision record on the previous revision. (Previous
because it always exists -- we can't obliterate revision 0.)

However it wouldn't hurt to investigate if we can, in fact, leave empty
revisons around after an obliterate. That would be most useful in
general because existing revision numbers would remain valid, and the
need to re-check-out a zillion working copies would almost vanish.

-- Brane

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-22 07:47:08 CEST

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.