From: Jonathan Tan <jonathantanmy@google.com>
To: git@vger.kernel.org
Cc: Jonathan Tan <jonathantanmy@google.com>, gitster@pobox.com
Subject: [PATCH v3 0/3] handle multiline in-body headers
Date: Tue, 20 Sep 2016 10:17:50 -0700 [thread overview]
Message-ID: <cover.1474391594.git.jonathantanmy@google.com> (raw)
In-Reply-To: <cover.1474319086.git.jonathantanmy@google.com>
Changes since v2:
o Removed utf8 translation before scissors line check in
check_inbody_header (I was thinking of support for encodings like
UTF-16, but I guess those don't work with the current reencode_string
anyway since it uses strlen internally)
With the above change, it is actually no longer necessary to make
is_scissors_line take plain char * (the second patch) - I think that
that patch still improves the code, but let me know if you want me to
remove it from this patch set.
Jonathan Tan (3):
mailinfo: separate in-body header processing
mailinfo: make is_scissors_line take plain char *
mailinfo: handle in-body header continuations
mailinfo.c | 116 +++++++++++++++++++++++++----------
mailinfo.h | 1 +
t/t4150-am.sh | 23 +++++++
t/t5100-mailinfo.sh | 2 +-
t/t5100/info0018 | 5 ++
t/t5100/info0018--no-inbody-headers | 5 ++
t/t5100/msg0015 | 2 -
t/t5100/msg0018 | 2 +
t/t5100/msg0018--no-inbody-headers | 8 +++
t/t5100/patch0018 | 6 ++
t/t5100/patch0018--no-inbody-headers | 6 ++
t/t5100/sample.mbox | 19 ++++++
12 files changed, 159 insertions(+), 36 deletions(-)
create mode 100644 t/t5100/info0018
create mode 100644 t/t5100/info0018--no-inbody-headers
create mode 100644 t/t5100/msg0018
create mode 100644 t/t5100/msg0018--no-inbody-headers
create mode 100644 t/t5100/patch0018
create mode 100644 t/t5100/patch0018--no-inbody-headers
--
2.10.0.rc2.20.g5b18e70
next prev parent reply other threads:[~2016-09-20 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 21:08 [PATCH v2 0/4] handle multiline in-body headers Jonathan Tan
2016-09-19 21:08 ` [PATCH v2 1/4] mailinfo: separate in-body header processing Jonathan Tan
2016-09-19 21:08 ` [PATCH v2 2/4] mailinfo: refactor to support utf8 decode attempts Jonathan Tan
2016-09-19 21:08 ` [PATCH v2 3/4] mailinfo: make is_scissors_line take plain char * Jonathan Tan
2016-09-19 21:08 ` [PATCH v2 4/4] mailinfo: handle in-body header continuations Jonathan Tan
2016-09-19 21:39 ` [PATCH v2 0/4] handle multiline in-body headers Junio C Hamano
2016-09-20 17:17 ` Jonathan Tan [this message]
2016-09-20 17:17 ` [PATCH v3 1/3] mailinfo: separate in-body header processing Jonathan Tan
2016-09-20 17:17 ` [PATCH v3 2/3] mailinfo: make is_scissors_line take plain char * Jonathan Tan
2016-09-20 17:17 ` [PATCH v3 3/3] mailinfo: handle in-body header continuations Jonathan Tan
2016-09-20 23:06 ` [PATCH v3 0/3] handle multiline in-body headers Jeff King
2016-09-21 17:24 ` 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.1474391594.git.jonathantanmy@google.com \
--to=jonathantanmy@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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.