From: Denton Liu <liu.denton@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Gmail munges dates?
Date: Thu, 12 Dec 2019 17:57:53 -0800 [thread overview]
Message-ID: <20191213015753.GA14249@generichostname> (raw)
Hi all,
It seems like Gmail is munging the dates on patches sent. Before today,
I've been sending patches out with mutt but I decided to switch to
git-send-email today since I was forwarding a patch that wasn't mine and
I wanted to preserve the date as part of the authorship information.
Unfortunately, it seems like mutt wasn't the culprit, it was Gmail
that's been munging the dates. For example, in this patch[1], the date
shows as
Date: Thu, 12 Dec 2019 16:44:50 -0800
even though locally, the output of the format-patch shows as
Date: Mon, 9 Dec 2019 19:25:34 +0100
So two questions related to this:
1. Is this something that we care about or is it okay to have fudged
dates? (I know all of my patches in each patchset only differ by a few
seconds and it seems like no one has noticed or cared so far)
2. Do we want to introduce a --in-body-date option or something to
format-patch which would include an in-body Date:, similar to the
in-body From:? (Also, while we're at it, maybe we could include an
--in-body-from to force that to happen since that's been a feature that
was requested in the past[2])
Thanks,
Denton
[1]: https://lore.kernel.org/git/8691ed2b84f7ee6b7c12d04d57a541bf22660333.1576197846.git.liu.denton@gmail.com/
[2]: https://lore.kernel.org/git/20191010225405.GA19475@sigill.intra.peff.net/
next reply other threads:[~2019-12-13 1:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 1:57 Denton Liu [this message]
2019-12-13 5:42 ` Gmail munges dates? Jeff King
2019-12-13 17:52 ` Junio C Hamano
2019-12-13 17:47 ` 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=20191213015753.GA14249@generichostname \
--to=liu.denton@gmail.com \
--cc=git@vger.kernel.org \
/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.