From: Matthew Wilcox <mawilcox@linuxonhyperv.com>
To: git@vger.kernel.org
Cc: Matthew Wilcox <mawilcox@microsoft.com>,
Jonathan Tan <jonathantanmy@google.com>
Subject: [PATCH 2/2] mailinfo: Understand forwarded patches
Date: Thu, 12 Jan 2017 01:20:24 -0800 [thread overview]
Message-ID: <1484212824-14108-2-git-send-email-mawilcox@linuxonhyperv.com> (raw)
In-Reply-To: <1484212824-14108-1-git-send-email-mawilcox@linuxonhyperv.com>
From: Matthew Wilcox <mawilcox@microsoft.com>
Extend the --scissors mechanism to strip off the preamble created by
forwarding a patch. There are a couple of extra headers ("Sent" and
"To") added by forwarding, but other than that, the --scissors option
will now remove patches forwarded from Microsoft Outlook to a Linux
email account.
Signed-off-by: Matthew Wilcox <mawilcox@microsoft.com>
---
mailinfo.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/mailinfo.c b/mailinfo.c
index 2059704a8..fc1275532 100644
--- a/mailinfo.c
+++ b/mailinfo.c
@@ -332,7 +332,7 @@ static void cleanup_subject(struct mailinfo *mi, struct strbuf *subject)
#define MAX_HDR_PARSED 10
static const char *header[MAX_HDR_PARSED] = {
- "From","Subject","Date",
+ "From","Subject","Date","Sent","To",
};
static inline int cmp_header(const struct strbuf *line, const char *hdr)
@@ -685,6 +685,13 @@ static int is_scissors_line(const char *line)
c++;
continue;
}
+ if (!memcmp(c, "Original Message", 16)) {
+ in_perforation = 1;
+ perforation += 16;
+ scissors += 16;
+ c += 15;
+ continue;
+ }
in_perforation = 0;
}
--
2.11.0
next prev parent reply other threads:[~2017-01-12 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 9:20 [PATCH 1/2] mailinfo: Add support for keep_cr Matthew Wilcox
2017-01-12 9:20 ` Matthew Wilcox [this message]
2017-01-12 18:17 ` [PATCH 2/2] mailinfo: Understand forwarded patches Jonathan Tan
2017-01-12 19:35 ` Matthew Wilcox
2017-01-12 20:18 ` Junio C Hamano
2017-01-12 18:04 ` [PATCH 1/2] mailinfo: Add support for keep_cr Jonathan Tan
2017-01-12 19:06 ` Matthew Wilcox
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=1484212824-14108-2-git-send-email-mawilcox@linuxonhyperv.com \
--to=mawilcox@linuxonhyperv.com \
--cc=git@vger.kernel.org \
--cc=jonathantanmy@google.com \
--cc=mawilcox@microsoft.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).