git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH RESEND] send-email: add 'specify-author' option

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Apr 6, 2012, 21:48 UTC
Message-ID
<CAMP44s1m2exUVRTzcBJrY8hnWxF+uEt58AQOP5vKiA3tfeRXRQ@mail.gmail.com>
In-Reply-To
<7vbon41ugg.fsf@alter.siamese.dyndns.org>
On Fri, Apr 6, 2012 at 11:22 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 22 quoted lines
> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>> On Fri, Apr 6, 2012 at 8:14 PM, Junio C Hamano <gitster@pobox.com> wrote:
>>> Felipe Contreras <felipe.contreras@gmail.com> writes:
>>>
>>>> Some mail servers (Microsoft Exchange) mangle the 'From' header, so
>>>> while applying the patches, the author has to be fixed manually.
>>> ...
>>> I wouldn't say that the existing option names to send-email are great, but
>>> I have to say that the one added by this is simply horrible ;-)
>>>
>>> The first paragraph of the proposed commit log message states the problem
>>> it tries to address very clearly, which is good, but is "From: " the only
>>> thing that needs this?  I am wondering if this should be named and behave
>>> more like "--duplicate-header" or "--in-body-header".
>>
>> I have never seen any other 'in-body-header' other than From, and I
>> don't see how that would be useful. Anybody else?
>
> The "Subject:" is very often used in the wild, when responding to an
> existing discussion thread with a patch, without changing the topic of the
> thread (I would say it is used more than "From: " override).
Hmm, but that is different, isn't it?
AFAIK people use this format:

--- $headers

Message

Patch (format-patch output: headers, commit message, diff) ---

In this case 'git am' would ignore the patch headers. The only way 'git am' would override $headers, is if the first part of the body has new headers:

--- $headers

$patch_headers
$patch_commit_message

$patch_diff ---

IOW; if there's no message at the beginning of the body.
> When using send-email to start a thread anew, this use case is much less
> of a problem, but I wouldn't be surprised if a broken MSA/MTA mangled the
> subject (especially imagine a non-ASCII ones) incorrectly which would be
> helped with exactly the same in-body-header mechanism.

I can't foresee that, but I guess we can do it anyway. So which would be the fields to repeat? From, Date, and Subject?

> You probably meant "I do not want to hear from Junio" by your last
> half-sentence, but I replied anyway ;-).
I meant I wanted to know which fields would be useful to put in the body.
Cheers.
-- 
Felipe Contreras
Previous: Junio C HamanoNext: Junio C Hamano
Message 6 of 14 in “send-email: add 'specify-author' option”
  1. send-email: add 'specify-author' optionFelipe Contreras, Apr 6, 2012
  2. Felipe ContrerasApr 6, 2012
  3. Junio C HamanoApr 6, 2012
  4. Felipe ContrerasApr 6, 2012
  5. Junio C HamanoApr 6, 2012
  6. Felipe ContrerasApr 6, 2012
  7. Junio C HamanoApr 6, 2012
  8. Felipe ContrerasApr 7, 2012
  9. Junio C HamanoApr 8, 2012
  10. Michael WittenApr 12, 2012
  11. Michael WittenApr 12, 2012
  12. Junio C HamanoApr 12, 2012
  13. Thomas RastApr 6, 2012
  14. Felipe ContrerasApr 6, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.