git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List Mailing <git@vger.kernel.org>
Subject: Re: "Problems" with git format-patch --thread email header ordering
Date: Fri, 15 Mar 2019 09:59:25 -0700	[thread overview]
Message-ID: <CAHk-=whe+R7fkTi0eBnhrBY=_k_du3e5dkNsVe=HgKXLoXekdg@mail.gmail.com> (raw)
In-Reply-To: <xmqqk1h09224.fsf@gitster-ct.c.googlers.com>

On Thu, Mar 14, 2019 at 9:47 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> Linus Torvalds <torvalds@linux-foundation.org> writes:
>
> > While it's true that header ordering isn't specified, there's a common
> > "canonical" order that the headers are listed in. To quote rfc822:
> > ...
> >             body must occur AFTER  the  headers.   It  is  recommended
> >             that,  if  present,  headers be sent in the order "Return-
> >             Path", "Received", "Date",  "From",  "Subject",  "Sender",
> >             "To", "cc", etc.
>
> I obviously won't do the last one myself, but if the issue is only
> to swap from and date, then this may be sufficient, perhaps?

I'm not actually sure _what_ the order requirements for gmail are,
since gmail itself doesn't seem to honor them. Does the order of the
Message-ID header line matter, for example?

I don't think it's the order of the From/Date lines, actually, because
google itself doesn't do that.

What Thomas Found out was that the exact same email with

    Message-Id/From/Date/Subject/To

(in that order) does not work, but

    Date/From/Subject/To/Message-Id

does work. Weird and "wonderful". But there might be a lot of other
orderings that work or don't.

Having looked through some other emails, I know that

    From/To/Subject/Date/Message-Id
    Subject/To/References/From/Message-ID/Date

also works.  Which makes me suspect that it's the Message-ID line that matters.

But it might be something _really_ odd, and maybe not just ordering at
all (ie it might be something where gmail wants to see the "From"
line, but only in certain circumstances, and only *then* does it
matter if the From line comes before some other line or not.

All we know is

 (a) gmail complains about the normal git format-patch ordering with a
"no From line" bounce

 (b) the same email with just headers re-ordered goes through

I *suspect* it's that Message-ID line, but .... It's very annoying.

               Linus

  reply	other threads:[~2019-03-15 16:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14 23:44 "Problems" with git format-patch --thread email header ordering Linus Torvalds
2019-03-15  4:47 ` Junio C Hamano
2019-03-15 16:59   ` Linus Torvalds [this message]
2019-04-04 18:06     ` Julian Andres Klode
2019-04-05  5:24       ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHk-=whe+R7fkTi0eBnhrBY=_k_du3e5dkNsVe=HgKXLoXekdg@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).