git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org, Nicolas Pitre <nico@cam.org>
Subject: Re: RFC: Allow missing objects during packing
Date: Mon, 11 Aug 2008 19:08:45 -0700	[thread overview]
Message-ID: <7vbpzzt26q.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080812012859.GT26363@spearce.org> (Shawn O. Pearce's message of "Mon, 11 Aug 2008 18:28:59 -0700")

"Shawn O. Pearce" <spearce@spearce.org> writes:

> If we are building a thin pack and one of the base objects we would
> consider for deltification is missing its OK, the other side already
> has that base object.  We may be able to get a delta from another
> object, or we can simply send the new object whole (no delta).
>
> This allows a shallow clone which may have only commits and trees
> (but only partial blobs) to generate a pack for a fetch client,
> so the shallow clone only needs to contain objects that are not
> in the common base.

I'd queue this to 'pu' (or 'next' if you want, but that amounts to about
the same thing as we will be rebuilding 'next' soon after 1.6.0 ships),
but this would probably be better demonstrated with a test script that
demonstrates in what workflow this would be useful.

  reply	other threads:[~2008-08-12  2:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-11 18:28 RFC: Allow missing objects during packing Shawn O. Pearce
2008-08-11 22:39 ` Junio C Hamano
2008-08-11 22:44   ` Shawn O. Pearce
2008-08-12  1:28     ` Shawn O. Pearce
2008-08-12  2:08       ` Junio C Hamano [this message]
2008-08-12  4:44       ` Nicolas Pitre
2008-08-12 16:41         ` [PATCH] pack-objects: Allow missing base objects when creating thin packs Shawn O. Pearce
2008-08-12 18:12           ` Nicolas Pitre
2008-08-12 18:18             ` Shawn O. Pearce
2008-08-12 18:26               ` Nicolas Pitre
2008-08-12 18:31                 ` [PATCH v2] " Shawn O. Pearce
2008-08-12 18:43                   ` Nicolas Pitre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vbpzzt26q.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=nico@cam.org \
    --cc=spearce@spearce.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).