From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: git@vger.kernel.org
Subject: Re: git send-email sets date
Date: Sun, 28 Jan 2018 15:15:36 +0000 [thread overview]
Message-ID: <20180128151536.GE431130@genre.crustytoothpaste.net> (raw)
In-Reply-To: <20180126183230.0ae0c76b@kitsune.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
On Fri, Jan 26, 2018 at 06:32:30PM +0100, Michal Suchánek wrote:
> git send-email sets the message date to author date.
>
> This is wrong because the message will most likely not get delivered
> when the author date differs from current time. It might give slightly
> better results with commit date instead of author date but can't is
> just skip that header and leave it to the mailer?
>
> It does not even seem to have an option to suppress adding the date
> header.
I'm pretty sure it's intended to work this way.
Without the Date header, we have no way of providing the author date
when sending a patch. git am will read this date and use it as the
author date when applying patches, so if it's omitted, the author date
will be wrong.
If you want to send patches with a different date, you can always insert
the patch inline in your mailer using the scissors notation, which will
allow your mailer to insert its own date while keeping the patch date
separate.
--
brian m. carlson / brian with sandals: Houston, Texas, US
https://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 867 bytes --]
next prev parent reply other threads:[~2018-01-28 15:15 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 [this message]
2018-01-28 15:56 ` Philip Oakley
2018-01-28 22:12 ` Theodore Ts'o
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180128151536.GE431130@genre.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=msuchanek@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.