git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Sergei Organov <osv@javad.com>
Cc: "Ask Bjørn Hansen" <ask@develooper.com>, git@vger.kernel.org
Subject: Re: [PATCH] Don't add To: recipients to the Cc: header
Date: Fri, 23 Nov 2007 11:48:48 -0800	[thread overview]
Message-ID: <7vejegu4in.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <87lk8orgpm.fsf@osv.gnss.ru> (Sergei Organov's message of "Fri, 23 Nov 2007 20:53:41 +0300")

Sergei Organov <osv@javad.com> writes:

> Junio C Hamano <gitster@pobox.com> writes:
>
>> Sergei Organov <osv@javad.com> writes:
>>
>>> Junio C Hamano <gitster@pobox.com> writes:
>>> [...]
>>>> Oops, forgot to say "no need to resend".  I asked only because I
>>>> wanted an independent datapoint for Emacs diff mode breakage.
>>>
>>> I bet I can damage any patch using any editor ;)
>>>
>>> More interesting is what version of Emacs it was?
>>
>> To be fair and honest, I do not think there is a simple fix for
>> this, although it probably is possible to fix it.
>>
>> What is causing the "breakage" is the fact that format-patch
>> output ends with the signature delimiter line "^-- $" that
>> immediately follows the patch text.
>
> Exactly. What causes breakage is the fact that the '-' character (as
> well as '+', ' ', '!', '#', and '\'), being the first symbol of a line
> has special meaning in the diff format.

That is correct only if they appear inside a hunk.  The number
of preimage and postimage lines in a hunk is recorded on the
hunk header line --- tools are given enough information to tell
a line that begins with a SP (or '+' or '-') outside a patch
from another such line that is inside the patch.

The diff editing mode of Emacs, at least the version that caused
this issue, however did not make use of that information.
That's the breakage.  Not format-patch output.

  reply	other threads:[~2007-11-23 19:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 11:00 [PATCH] Don't add To: recipients to the Cc: header Ask Bjørn Hansen
2007-11-19 11:05 ` Ask Bjørn Hansen
2007-11-20  7:52 ` Junio C Hamano
2007-11-20  9:36   ` Ask Bjørn Hansen
2007-11-20 19:04     ` Junio C Hamano
2007-11-20 19:18       ` Sergei Organov
2007-11-20 20:21         ` Junio C Hamano
2007-11-23 17:53           ` Sergei Organov
2007-11-23 19:48             ` Junio C Hamano [this message]
2007-11-23 20:18               ` Sergei Organov
2007-11-23 23:54                 ` Junio C Hamano
2007-11-26 13:48                   ` Sergei Organov
2007-11-26 16:53                     ` Junio C Hamano
2007-11-26 18:29                       ` Sergei Organov

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=7vejegu4in.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=ask@develooper.com \
    --cc=git@vger.kernel.org \
    --cc=osv@javad.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).