zimoun writes: > Hi Chris, > > On Mon, 16 Nov 2020 at 19:28, Christopher Baines wrote: > >>> I recently have a very similar issue [1]. And based on my >>> investigations [2], the issue seems "commit date vs author date"; >>> especially when merges are floating around. Because of that, from >>> "From" to "To" is not always accurate. Chris, could you confirm? >>> >>> 1: >>> 2: >> >> The Guix Data Service stores the date in the email from the Git hook >> that runs when one pushes to Savannah. That's the date you see for a >> revision, and it should be pretty close to when it actually showed up in >> the Git repository. It's not perfectly accurate, but it should be better >> than either the commit date or author date from the Git metadata. > > Re-reading [2] above, I am confused. Because the Data Service seems to > show the author date rather than the commit date or the header email > date. > > The email database from where the Data Service is fetching is > guix-commits, right? > > If yes, there is different dates that are appearing; for instance the > first I find: commit 5627bfe45ce46f498979b4ad2deab1fdfed22b6c authored > by Jason Conroy and pushed by mothacehe: > > --8<---------------cut here---------------start------------->8--- > From MAILER-DAEMON Thu Oct 01 03:28:02 2020 > Date: Thu, 01 Oct 2020 03:27:57 -0400 > X-List-Received-Date: Thu, 01 Oct 2020 07:28:00 -0000 > -- > AuthorDate: Sun Sep 27 13:16:39 2020 -0400 > --8<---------------cut here---------------end--------------->8--- > > Message-ID: <20201001072757.23203.96292@vcs0.savannah.gnu.org> > > > And from my Git checkout: CommitDate: Thu Oct 1 09:27:33 2020 +0200. > > (Modulo some timezone conversion, I guess.) > > > Maybe my investigations in [2] above are wrong but which date from the > email the Data Service is using? > > > I agree the most accurate is the date from the email header of > guix-commits. So the date given by data.guix.gnu.org for this revision is: 2020-10-01 07:27:57 [1] 1: https://data.guix.gnu.org/revision/5627bfe45ce46f498979b4ad2deab1fdfed22b6c Unfortunately, it's not explicit about the timezone, but it's UTC. This matches the date in the email, as you include it above: It's just expressed in a different timezone.