From: Florian Weimer <fw@deneb.enyo.de>
To: git@vger.kernel.org
Subject: git mailinfo with patch parser
Date: Wed, 02 Oct 2019 06:43:35 +0200 [thread overview]
Message-ID: <87imp77o5k.fsf@mid.deneb.enyo.de> (raw)
git mailinfo splits a message into headers, commit message, and patch
text, but does not actually parse the patch text. As a result, the
patch portion produced by git mailinfo can contain something that
looks like a patch, but actually isn't.
Is there a way to get the patch data, as parsed by git apply or git
am, and dump it back in patch format, without actually applying the
patch to a working tree?
next reply other threads:[~2019-10-02 4:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 4:43 Florian Weimer [this message]
2019-10-02 5:35 ` git mailinfo with patch parser Junio C Hamano
2019-10-02 5:41 ` Florian Weimer
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=87imp77o5k.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=git@vger.kernel.org \
/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.