[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YBhBfdZecMscxPOE@mit.edu>
Date: Mon, 1 Feb 2021 12:59:25 -0500
From: "Theodore Ts'o" <tytso@....edu>
To: Lukas Bulwahn <lukas.bulwahn@...il.com>
Cc: Greg KH <gregkh@...uxfoundation.org>,
Dwaipayan Ray <dwaipayanray1@...il.com>,
Joe Perches <joe@...ches.com>,
linux-kernel-mentees@...ts.linuxfoundation.org,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Linux-kernel-mentees] Patches from the future - can checkpatch
help?
On Mon, Feb 01, 2021 at 05:50:45PM +0100, Lukas Bulwahn wrote:
>
> Dwaipayan, there are two ways:
> - We build a bot listening to mailing lists and check. I like that
> implementation idea for various other checks.
> - Stephen Rothwell could include this as a check on linux-next and
> inform the git author and committer.
>
> I am wondering though if that is worth the effort, three instances of
> a wrong date among 1M commits seems to be very seldom and the harm of
> that mistake is quite small as well.
Another solution might be to ask the git developers if they would be
willing to have "git am" print a warning if the date is sufficiently
insane (say, more than 3 months in the past or present).
One could also imagine a request that "git log" would have a new
format where normally the author time is printed, but if it's
sufficiently different from the commit time, the commit time is also
printed in parenthesis.
Or you could set up your git config so that "git log" uses
--pretty=fuller by default, which prints both the author date and
commit date.
Like Lukas, I'm not really sure it's worth the effort, however.
- Ted
Powered by blists - more mailing lists