From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Tan <jonathantanmy@google.com>
Cc: git@vger.kernel.org, peff@peff.net
Subject: Re: [RFC/PATCH 0/3] handle multiline in-body headers
Date: Fri, 16 Sep 2016 11:29:27 -0700 [thread overview]
Message-ID: <xmqqshszk8ag.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <cover.1474047135.git.jonathantanmy@google.com> (Jonathan Tan's message of "Fri, 16 Sep 2016 10:37:21 -0700")
Jonathan Tan <jonathantanmy@google.com> writes:
> Thanks, Peff, for the explanation and the method to reproduce the issue.
>
> The issue seems to be in mailinfo.c - this patch set addresses that, and I have
> also included a test for "git am" in t/t4150-am.sh to show the effect of this
> patch set on that command.
Thanks, will take a look.
> Jonathan Tan (3):
> mailinfo: refactor commit message processing
> mailinfo: correct malformed test example
> mailinfo: handle in-body header continuations
>
> mailinfo.c | 165 ++++++++++++++++++++++++++++-------
> mailinfo.h | 1 +
> t/t4150-am.sh | 23 +++++
> t/t5100-mailinfo.sh | 4 +-
> t/t5100/info0008--no-inbody-headers | 5 ++
> t/t5100/info0018 | 5 ++
> t/t5100/msg0008--no-inbody-headers | 6 ++
> t/t5100/msg0015--no-inbody-headers | 1 +
> t/t5100/msg0018 | 2 +
> t/t5100/patch0008--no-inbody-headers | 0
> t/t5100/patch0018 | 6 ++
> t/t5100/sample.mbox | 20 +++++
> 12 files changed, 206 insertions(+), 32 deletions(-)
> create mode 100644 t/t5100/info0008--no-inbody-headers
> create mode 100644 t/t5100/info0018
> create mode 100644 t/t5100/msg0008--no-inbody-headers
> create mode 100644 t/t5100/msg0018
> create mode 100644 t/t5100/patch0008--no-inbody-headers
> create mode 100644 t/t5100/patch0018
next prev parent reply other threads:[~2016-09-16 18:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 19:58 [PATCH] sequencer: support folding in rfc2822 footer Jonathan Tan
2016-09-03 2:23 ` Junio C Hamano
2016-09-06 22:08 ` Jonathan Tan
2016-09-06 23:30 ` Jonathan Tan
2016-09-07 6:38 ` Jeff King
2016-09-16 17:37 ` [RFC/PATCH 0/3] handle multiline in-body headers Jonathan Tan
2016-09-16 18:29 ` Junio C Hamano [this message]
2016-09-16 17:37 ` [RFC/PATCH 1/3] mailinfo: refactor commit message processing Jonathan Tan
2016-09-16 19:12 ` Junio C Hamano
2016-09-16 21:46 ` Jeff King
2016-09-16 17:37 ` [RFC/PATCH 2/3] mailinfo: correct malformed test example Jonathan Tan
2016-09-16 19:19 ` Junio C Hamano
2016-09-16 22:42 ` Jonathan Tan
2016-09-16 22:55 ` Junio C Hamano
2016-09-17 0:31 ` Jonathan Tan
2016-09-17 3:48 ` Junio C Hamano
2016-09-16 17:37 ` [RFC/PATCH 3/3] mailinfo: handle in-body header continuations Jonathan Tan
2016-09-16 20:17 ` Junio C Hamano
2016-09-16 20:49 ` Jonathan Tan
2016-09-16 20:59 ` Junio C Hamano
2016-09-16 22:36 ` Jonathan Tan
2016-09-16 23:04 ` Junio C Hamano
2016-09-17 0:22 ` Jonathan Tan
2016-09-16 21:51 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqshszk8ag.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jonathantanmy@google.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).