From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2016, #08; Thu, 26)
Date: Sat, 18 Jun 2016 18:19:23 -0700 [thread overview]
Message-ID: <xmqqy462x9es.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160527003621.GB26262@sigill.intra.peff.net> (Jeff King's message of "Thu, 26 May 2016 20:36:21 -0400")
Jeff King <peff@peff.net> writes:
> On Thu, May 26, 2016 at 03:50:14PM -0700, Junio C Hamano wrote:
>
>> * jk/upload-pack-hook (2016-05-24) 6 commits
>> - upload-pack: provide a hook for running pack-objects
>> - config: add a notion of "scope"
>> - config: return configset value for current_config_ functions
>> - config: set up config_source for command-line config
>> - git_config_parse_parameter: refactor cleanup code
>> - git_config_with_options: drop "found" counting
>>
>> Allow a custom "git upload-pack" replacement to respond to
>> "fetch/clone" request.
>>
>> Will merge to 'next'.
>
> I just sent a replacement for the fourth patch that avoids the t/helper
> problem. It's probably worth dealing with before even hitting "next" so
> as not to break bisection.
>
> You should probably hold off on merging the top one. The discussion
> stalled because I was on vacation, but it has resumed now (the earlier
> refactoring bits are uncontroversial, I think).
And then it seems nothing happened. Can we settle this soonish?
next prev parent reply other threads:[~2016-06-19 1:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 22:50 What's cooking in git.git (May 2016, #08; Thu, 26) Junio C Hamano
2016-05-27 0:36 ` Jeff King
2016-05-27 2:11 ` Junio C Hamano
2016-06-19 1:19 ` Junio C Hamano [this message]
2016-06-19 10:10 ` Jeff King
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=xmqqy462x9es.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.