backward diffs in knits?

[Robert Collins]

On Wed, 2007-04-11 at 09:59 -0500, John Arbash Meinel wrote:
> Robert Collins wrote:
> ...
> 
> >> I don't think backwards deltas should be generated "on-the-fly",
> >> because
> >> of the potential for a new corruption to lose old data.
> > 
> > I'm not sure what you mean here, in particular you can always perform a
> > check of all data after the pull, if and only if we have altered
> > representation.
> 
> I was thinking more at "per-commit" time, not so much at 'pull' time.
> Simply because commit really only works with one revision at a time, and
> it doesn't seem like you want to do a full integrity check, etc.
> 
> But pull will usually be operating on more (and also transmitting them
> over the wire).

But commit adds a single revision, it cannot (in append only mode -
which I have not suggested changing) create backward deltas.

Perhaps I'm confused by what you mean?

-Rob
-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20070412/4a6e1bb5/attachment.pgp