From: Matt Keenan <matt.keenan@oracle.com>
To: meta@public-inbox.org
Cc: matt.keenan@oracle.com
Subject: Issue with lore GIT repo for linux-kernel
Date: Fri, 27 Aug 2021 20:57:44 +0100 [thread overview]
Message-ID: <572a196d-8550-7460-93fd-6e75cfd671d9@oracle.com> (raw)
Hi,
Reaching out to you as suggested by Konstantin (webmaster@kernel.org),
to whom I sent the following email, and he recommended on contact you
illustrating my suggestion that commits to lore mail lists can happily
have any AuthorDate they want, but the CommitDate should really reflect
the actual date/time the commit was made.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Just wanted to make you aware of something I find a little odd regarding
the latest git shard for linux-kernel mailing list.
Commit: a3d6603dc01612c65db315bdcf980487293c41e9 to
https://lore.kernel.org/lkml/10
This is the 30th anniversary of Linus's original post "What would you
like to see most in minix?".
Because the AuthorDate for this message is 25-Aug-1991, the resulting
CommitDate is also set to 25-Aug-1991, even though the actual commit to
10.git took place on 25-Aug-2021.
This breaks some git commands for 10.git. Specifically for those who
want to use --after git option.
10.git contains emails from 10-May-2021 to the present day. If one wants
to see messages from say 23-Aug-2021, one should be able to use the
following :
$ git log --date=local --pretty='%H %cd' --after='2021-08-22 23:59:59'
--before='2021-08-24 00:00:00'
This command sadly produces no output and all because of commit
a3d6603dc01612c65db315bdcf980487293c41e9.
Git will start at HEAD, and check the CommitDate for each commit. If the
CommitDate falls between the boundaries of --after and --before it's
printed. Traversal will then cease when it reachs the first commit with
a CommitDate older than --after.
Git therefore traverses only as far as
a3d6603dc01612c65db315bdcf980487293c41e9, sees a date older than
22-Aug-2021 and then stops.
Git is I presume making the assuption that all commits have CommitDate's
that are in chronological order, however because of
a3d6603dc01612c65db315bdcf980487293c41e9, commits to 10.git are not.
Therefore this commit sadly but effectively renders --after useless for
the 10.git lkml repo for any dates prior to 26-Aug-2021.
I'm not a git expert, as such don't have any recommendations for
possibly resolving this, or whether you feel this is something that
needs to be resolved or not.
I'm not a git expert, as such don't have any recommendations for
possibly resolving this, or whether you feel this is something that
needs to be resolved or not. Personally the AuthorDate for this commit
can happily remain at 1991, but the CommitDate I think should really
reflect when the actual commit to 10.git took place.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Anyhow I hope you find this information useful.
regards
Matt
next reply other threads:[~2021-08-27 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 19:57 Matt Keenan [this message]
2021-08-27 20:50 ` Issue with lore GIT repo for linux-kernel Eric Wong
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: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=572a196d-8550-7460-93fd-6e75cfd671d9@oracle.com \
--to=matt.keenan@oracle.com \
--cc=meta@public-inbox.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 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).