From: Junio C Hamano <gitster@pobox•com>
To: Stefan Beller <sbeller@google•com>
Cc: "git\@vger.kernel.org" <git@vger•kernel.org>
Subject: Re: What's cooking in git.git (Jan 2017, #04; Mon, 23)
Date: Wed, 25 Jan 2017 12:35:16 -0800 [thread overview]
Message-ID: <xmqqwpdianej.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAGZ79kZKDyfP1SPsxAf8oMSU3763QiogLpUzFZHy+OTQQdJP6A@mail.gmail.com> (Stefan Beller's message of "Wed, 25 Jan 2017 10:38:32 -0800")
Stefan Beller <sbeller@google•com> writes:
> On Mon, Jan 23, 2017 at 4:18 PM, Junio C Hamano <gitster@pobox•com> wrote:
>>
>> * sb/unpack-trees-super-prefix (2017-01-12) 5 commits
>> - SQUASH
>> - unpack-trees: support super-prefix option
>> - t1001: modernize style
>> - t1000: modernize style
>> - read-tree: use OPT_BOOL instead of OPT_SET_INT
>>
>> "git read-tree" and its underlying unpack_trees() machinery learned
>> to report problematic paths prefixed with the --super-prefix option.
>>
>> Expecting a reroll.
>> The first three are in good shape. The last one needs a better
>> explanation and possibly an update to its test.
>> cf. <CAGZ79kaHDnVLQr8WLoaD5KKs7EqeW=KbkptF=iHpU5t054Xcdw@mail•gmail.com>
>>
>
> Please see
> https://public-inbox.org/git/20170118010520.8804-1-sbeller@google.com/
Thanks, applied. Let's move this forward.
prev parent reply other threads:[~2017-01-25 20:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 0:18 What's cooking in git.git (Jan 2017, #04; Mon, 23) Junio C Hamano
2017-01-24 10:04 ` Lars Schneider
2017-01-24 13:27 ` Jeff King
2017-01-24 14:43 ` Lars Schneider
2017-01-25 17:01 ` Johannes Schindelin
2017-01-25 17:39 ` Jeff King
2017-01-25 18:16 ` Junio C Hamano
2017-01-25 18:39 ` Jeff King
2017-01-25 22:51 ` Junio C Hamano
2017-01-26 9:14 ` Lars Schneider
2017-01-26 9:48 ` Lars Schneider
2017-01-26 14:26 ` Jeff King
2017-01-26 18:05 ` Junio C Hamano
2017-01-25 18:38 ` Stefan Beller
2017-01-25 20:35 ` Junio C Hamano [this message]
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=xmqqwpdianej.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=sbeller@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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