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

Re: Maintaining NodeID sanity

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-05-10 21:52:29 CEST

Branko Čibej <brane@xbc.nu> writes:
> Just two comments from me; Bill, Mike and I hashed them out on #svn:

Incidentally, excuse me for neglecting to thank you (Brane) along with
Bill for spending so much time hashing this stuff out. It's just that
I wasn't on IRC for those discussions; but I did hear about them. Oh
yes. I certainly _did_ _hear_ about them :-).

> * Give the root directory in revision 0 and initial copy id of 0.
> This means that:
> o You have a nice, handy value for initializing the copies table
> o Every node will get a copy id, making node numbering more
> consistent and incidentally promoting branches to
> first-class status


> * Swap the txn and copy id in the key, making it "node.copy.txn".
> This will cause related keys to be clustered closer together,
> making relatedness searches faster.

+1 again.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 10 21:53:05 2002

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.