From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Taylor Blau <me@ttaylorr.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2017, #01; Wed, 4)
Date: Wed, 04 Oct 2017 17:46:21 +0900 [thread overview]
Message-ID: <xmqqr2ujb8rm.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20171004083111.5y7su63scydg2yzk@sigill.intra.peff.net> (Jeff King's message of "Wed, 4 Oct 2017 04:31:11 -0400")
Jeff King <peff@peff.net> writes:
>> - pretty.c: delimit "%(trailers)" arguments with ","
>>
>> "git for-each-ref --format=..." learned a new format element,
>> %(trailers), to show only the commit log trailer part of the log
>> message.
>>
>> Will merge to 'next'.
>
> I think we want the first patch of this series to graduate before v2.15,
> even if the rest doesn't make it. It tweaks a new syntax introduced
> earlier in this cycle by jk/trailers-parse. If we ship without the
> tweak, then we'll have to support the colon-delimiter to remain
> backwards-compatible.
Yeah, thanks for reminding me. I actually was hoping that this will
prove to be stable enough by the time -rc1 gets tagged, but yes, the
bottom one looks innocuous/safe enough and should be fast-tracked to
'master' soonish.
Thanks.
next prev parent reply other threads:[~2017-10-04 8:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 7:19 What's cooking in git.git (Oct 2017, #01; Wed, 4) Junio C Hamano
2017-10-04 8:02 ` Jeff King
2017-10-04 8:24 ` Jeff King
2017-10-04 8:31 ` Jeff King
2017-10-04 8:46 ` Junio C Hamano [this message]
2017-10-04 18:07 ` Taylor Blau
2017-10-05 5:21 ` 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=xmqqr2ujb8rm.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--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.