Introduction to history deltas

[Michael Ellerman]

On Thu, 8 Dec 2005 12:43, Jan Hudec wrote:
> 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.

Sorry, terminology clash there.

I'm talking about being able to branch from a project but not get the history, 
so you can do super cheap branches when all you care about is making a change 
on top of the current sources.

cheers

-- 
Michael Ellerman
IBM OzLabs

email: michael:ellerman.id.au
inmsg: mpe:jabber.org
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051208/c8922f4d/attachment.pgp