Introduction to history deltas

[Jan Hudec]

On Thu, Dec 08, 2005 at 12:14:17 -0600, Michael Ellerman wrote:
> On Thu, 8 Dec 2005 10:51, Matt Lavin wrote:
> > Aaron Bentley wrote:
> > > Right.  So one way of looking at it is as a hunk organization method.
> > > You would either organize hunks by file (like weaves do) or by revision
> > > (history deltas).
> >
> > Hopefully this will not be a completely off-topic comment, but if a goal
> > of bzr is to ever support a partial checkout of a tree then it seems
> > like it would be better to have the data organized by file, not
> > revision.  Maybe not,  but I thought I'd throw it out there anyway.
> 
> Only if by "partial" you mean "checkout a subset of files". When I think of a 
> "partial" checkout I think "checkout a subset of history", in which case 
> per-revision storage might be preferable. Swings and roundabouts.

I see "checkout" as related to archive branches -- there is no history
in checkout at all.

By the way, I even think branching just part of the files might be
useful. Perhaps you have a large project that evolved into several
libraries, that you now want to split and maybe combine them in another
project. And then sometimes merge between those two projects.

-- 
						 Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051208/26e58129/attachment.pgp