From: Jonathan Tan <jonathantanmy@google.com>
To: git@vger.kernel.org
Cc: Jonathan Tan <jonathantanmy@google.com>,
peff@peff.net, gitster@pobox.com
Subject: [RFC/PATCH 0/3] handle multiline in-body headers
Date: Fri, 16 Sep 2016 10:37:21 -0700 [thread overview]
Message-ID: <cover.1474047135.git.jonathantanmy@google.com> (raw)
In-Reply-To: <20160907063819.dd7aulnlsytcuyqj@sigill.intra.peff.net>
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.
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
--
2.10.0.rc2.20.g5b18e70
next prev parent reply other threads:[~2016-09-16 17:37 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 ` Jonathan Tan [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
2016-09-16 18:29 ` [RFC/PATCH 0/3] handle multiline in-body headers 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=cover.1474047135.git.jonathantanmy@google.com \
--to=jonathantanmy@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.