From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Nicolas Pitre <nico@cam.org>
Subject: Re: RFC: Allow missing objects during packing
Date: Mon, 11 Aug 2008 15:44:04 -0700 [thread overview]
Message-ID: <20080811224404.GQ26363@spearce.org> (raw)
In-Reply-To: <7vk5enuqfg.fsf@gitster.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> wrote:
> "Shawn O. Pearce" <spearce@spearce.org> writes:
>
> > ... It seems pretty harmless to allow an object we
> > aren't going to transmit but that we want to use as a delta base
> > in a thin pack to be missing. At worst we just get a little bit
> > more data transfer.
>
> If the check is only about a thin delta base that is not going to be
> transmit, I'd agree. But I do not see how you are distinguishing that
> case and the case where an object you are actually sending is missing (in
> which case we would want to error out, wouldn't we?)
Arrgh. Good catch. My patch is flawed in that it does not correctly
fail if we really needed the missing object in this output pack.
I don't think that would be hard to fix. I'll respin something
shortly.
--
Shawn.
next prev parent reply other threads:[~2008-08-11 22:45 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 [this message]
2008-08-12 1:28 ` Shawn O. Pearce
2008-08-12 2:08 ` Junio C Hamano
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=20080811224404.GQ26363@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nico@cam.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).