From: Andreas Schwab <schwab@linux-m68k.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
git@vger.kernel.org
Subject: Re: Getting clean diff data from git-mailinfo
Date: Sat, 22 Feb 2020 19:00:43 +0100 [thread overview]
Message-ID: <87sgj2fqno.fsf@igel.home> (raw)
In-Reply-To: <xmqqftf27e8n.fsf@gitster-ct.c.googlers.com> (Junio C. Hamano's message of "Sat, 22 Feb 2020 08:56:08 -0800")
On Feb 22 2020, Junio C Hamano wrote:
> *1* Even when people edit without changing the line numbers (imagine
> a typofix on a '+' line), I saw that "patch" mode of Emacs broke
> the line count on "@@ ...@@" line of the last hunk when the
> patch ends with certain patterns.
For example, when followed by the "-- " signature of git format-patch,
as that makes the output ambiguous.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2020-02-22 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 17:14 Getting clean diff data from git-mailinfo Konstantin Ryabitsev
2020-02-22 16:47 ` Junio C Hamano
2020-02-22 16:56 ` Junio C Hamano
2020-02-22 18:00 ` Andreas Schwab [this message]
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=87sgj2fqno.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=konstantin@linuxfoundation.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 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).