git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] pack-objects: disable pack reuse for object-selection options
Date: Mon, 8 May 2017 22:21:14 -0400	[thread overview]
Message-ID: <20170509022114.s3tpxrgtplsopr4x@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqfuge6akl.fsf@gitster.mtv.corp.google.com>

On Tue, May 09, 2017 at 11:14:18AM +0900, Junio C Hamano wrote:

> Jeff King <peff@peff.net> writes:
> 
> >> Ah, OK, and now I understand why you called this a "bug" (which is
> >> older and do not need to be addressed as part of 2.13) in the
> >> original message.  The new tests check requests that ought to
> >> produce an empty packfile as the result actually do, but with the
> >> current code, the reuse code does not work with --local and friends
> >> and ends up including what was requested to be excluded.
> >
> > Right. Did you want me to try re-wording the commit message, or does it
> > make sense now?
> 
> It does make sense to me now, but I do not speak for all future
> readers of "git log", so...

I guess what I was asking was: do you still think it was unclear, or do
you think you were just being dense?

I don't feel like I gave any information in the follow-on explanation
that wasn't in the commit message, so I wasn't clear if I worded it
better or if it just sunk in better.

-Peff

  reply	other threads:[~2017-05-09  2:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02  8:43 [PATCH] pack-objects: disable pack reuse for object-selection options Jeff King
2017-05-08  4:56 ` Junio C Hamano
2017-05-08  7:31   ` Jeff King
2017-05-09  0:44     ` Junio C Hamano
2017-05-09  2:00       ` Jeff King
2017-05-09  2:14         ` Junio C Hamano
2017-05-09  2:21           ` Jeff King [this message]
2017-05-09  2:48             ` Junio C Hamano
2017-05-09  2:54               ` Jeff King
2017-05-09  2:59                 ` Jeff King
2017-05-09  3:08                 ` Junio C Hamano

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=20170509022114.s3tpxrgtplsopr4x@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).