History horizons spec

John A Meinel john at arbash-meinel.com
Mon Feb 27 04:02:18 GMT 2006


Aaron Bentley wrote:
> Hi all,
> 
> One of the few things I used the obsolete documents for was as a
> reference to 'history horizons'.  So I've put an updated spec (In
> Canonical spec format) up at http://bazaar-vcs.org/HistoryHorizon
> 
> I don't expect this to appear in say, bzr 0.9, but it is somewhere, err,
> on the horizon.
> 
> I believe horizons remain a relevant idea, because they provide a middle
> ground between space/time-eating standalone working trees and checkouts,
> which are slow when the repository is remote, and useless when the
> repository is disconnected.
> 
> Comments, criticism, flames, etc., welcome.
> 
> Aaron

Ultimately, I think it will be nice to have some sort of
check-pointing/history horizon system, so that new branches don't have
to contain all of history.

I think it would make more sense to do it as a remote reference, though.
So you could say, "this is the history I have, for older ancestors, look
here..."

I think we could still keep the ancestry graph for them, just to make
things easier. I would like to see us keep a revision_id, parent_ids,
and testament sha1. That way we can maintain historical integrity, as
well as selecting merge bases, etc.

And by having the 'remote reference', if you don't have all the data
here, you have an idea where you can go fetch it to finished doing your
work.

John
=:->

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060226/5a1a9316/attachment.pgp 


More information about the bazaar mailing list