From: Jonathan Tan <jonathantanmy@google.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Stefan Beller <sbeller@google.com>
Subject: Re: What's cooking in git.git (Oct 2016, #07; Wed, 26)
Date: Wed, 26 Oct 2016 15:42:21 -0700 [thread overview]
Message-ID: <50f4e0b0-c044-be57-4e08-08d9970fe4a4@google.com> (raw)
In-Reply-To: <xmqq4m3ybv7h.fsf@gitster.mtv.corp.google.com>
On 10/26/2016 03:29 PM, Junio C Hamano wrote:
> * jt/trailer-with-cruft (2016-10-21) 8 commits
> - trailer: support values folded to multiple lines
> - trailer: forbid leading whitespace in trailers
> - trailer: allow non-trailers in trailer block
> - trailer: clarify failure modes in parse_trailer
> - trailer: make args have their own struct
> - trailer: streamline trailer item create and add
> - trailer: use list.h for doubly-linked list
> - trailer: improve const correctness
>
> Update "interpret-trailers" machinery and teaches it that people in
> real world write all sorts of crufts in the "trailer" that was
> originally designed to have the neat-o "Mail-Header: like thing"
> and nothing else.
>
> Waiting for review.
For this patch set, should I look for another reviewer? In the e-mail
thread [1], you and Stefan seemed positive about this patch set.
(I've also checked [2] that this is not merged yet.)
[1] <cover.1477072247.git.jonathantanmy@google.com>
[2] git log --grep='jt/trailer'
next prev parent reply other threads:[~2016-10-26 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 22:29 What's cooking in git.git (Oct 2016, #07; Wed, 26) Junio C Hamano
2016-10-26 22:42 ` Jonathan Tan [this message]
2016-10-26 22:47 ` 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=50f4e0b0-c044-be57-4e08-08d9970fe4a4@google.com \
--to=jonathantanmy@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.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).