europython sprint report wrapup
Aaron Bentley
aaron.bentley at utoronto.ca
Mon Jul 16 18:24:26 BST 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Robert Collins wrote:
> To wrap up the lithuanian post-europython sprint...
Thanks for keeping us in the loop.
> Jelmer has 'branch -r -5.. working, which will only copy the data for
> the last 5 revisions. This is the key starting point for
> ShallowBranches/HistoryHorizons. Woot!
In London, Jelmer and I discussed why we were arguing so strongly about
History Horizons. We concluded that Jelmer wants a related feature:
Lazy Repositories.
Unlike History Horizons, Lazy Repositories make a branch dependent on
its upstream branch for old revisions, and do not provide a hard
guarantee that revisions past the history horizon will *never* be
stored. If old revisions are required, (e.g. to perform a merge,) they
will be fetched and stored in the local repository at that time.
By contast, history horizons are intended to serve the case where
there's a desire to omit old data permanently, e.g. when web space is
limited. For the local branching case, my desire was that branches with
history horizons would contain all the data necessary to perform a
merge. This made annotate-based merge especially desirable, because it
doesn't require a base revision.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGm6nK0F+nu1YWqI0RAlu6AJ99ijrXfeNtLGF4XmJpdHTV981CXQCfRich
jpU9u6pA9egIwSJuJ4JmBKY=
=xT1e
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list