From: Theodore Ts'o <tytso@mit.edu>
To: Philip Oakley <philipoakley@iee.org>
Cc: "'Michal Suchánek'" <msuchanek@suse.de>,
git@vger.kernel.org,
"'brian m. carlson'" <sandals@crustytoothpaste.net>
Subject: Re: git send-email sets date
Date: Sun, 28 Jan 2018 17:12:31 -0500 [thread overview]
Message-ID: <20180128221231.GB13621@thunk.org> (raw)
In-Reply-To: <001601d39850$a0a48ae0$e1eda0a0$@iee.org>
On Sun, Jan 28, 2018 at 03:56:57PM -0000, Philip Oakley wrote:
> Michal, you may want to hack up an option that can automatically create
> that format if it is of use. I sometimes find the sort order an issue in
> some of my mail clients.
If there is a From: header in the beginning of the mail body, it is
used as the Author instead of the From: header in the mail header. It
would make sense if there is a Date: header in the beginning of the
mail body, it should be used instead of Date: field in the mail header.
The problem is that if existing git clients don't support this, it
wouldn't be safe to start emmiting patches with that format for at
least a year or two until the prerequisite version of git gets wide
adoption. Alternatively, there could be a git option which causes
something like X-Git-Author-Date: to be set in the mail header.
- Ted
next prev parent reply other threads:[~2018-01-28 22:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 17:32 git send-email sets date Michal Suchánek
2018-01-28 15:15 ` brian m. carlson
2018-01-28 15:56 ` Philip Oakley
2018-01-28 22:12 ` Theodore Ts'o [this message]
2018-01-30 20:41 ` Junio C Hamano
2018-01-28 22:32 ` Ævar Arnfjörð Bjarmason
2018-01-29 12:48 ` Eric Wong
2018-01-30 20:37 ` 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=20180128221231.GB13621@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=msuchanek@suse.de \
--cc=philipoakley@iee.org \
--cc=sandals@crustytoothpaste.net \
/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).