From: Christopher Baines <mail@cbaines.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Data Services: use cases
Date: Mon, 16 Nov 2020 20:54:09 +0000 [thread overview]
Message-ID: <87blfxm39q.fsf@cbaines.net> (raw)
In-Reply-To: <86a6vhqcc3.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2429 bytes --]
zimoun <zimon.toutoune@gmail.com> writes:
> Hi Chris,
>
> On Mon, 16 Nov 2020 at 19:28, Christopher Baines <mail@cbaines.net> 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: <https://lists.gnu.org/archive/html/guix-devel/2020-10/msg00084.html>
>>> 2: <https://lists.gnu.org/archive/html/guix-devel/2020-10/msg00096.html>
>>
>> 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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2020-11-16 20:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 13:26 Data Services: use cases zimoun
2020-10-13 8:44 ` Pierre Neidhardt
2020-10-21 9:27 ` Ludovic Courtès
2020-10-21 9:39 ` Pierre Neidhardt
2020-10-21 10:19 ` zimoun
2020-11-16 19:28 ` Christopher Baines
2020-11-16 20:24 ` zimoun
2020-11-16 20:54 ` Christopher Baines [this message]
2020-11-16 21:12 ` zimoun
2020-11-16 21:50 ` Christopher Baines
2020-11-16 22:38 ` zimoun
2020-11-17 21:43 ` zimoun
2020-11-17 21:57 ` Fix incorrect date and commit in Data Service zimoun
2020-11-17 22:44 ` zimoun
2020-11-16 19:26 ` Data Services: use cases Christopher Baines
2020-11-16 19:20 ` Christopher Baines
2020-11-17 7:48 ` Pierre Neidhardt
2020-11-17 8:04 ` Christopher Baines
2020-11-17 8:49 ` Pierre Neidhardt
2020-11-17 19:34 ` Christopher Baines
2020-11-17 19:42 ` Pierre Neidhardt
2020-11-16 19:17 ` Christopher Baines
2020-11-16 20:34 ` zimoun
2020-11-16 21:08 ` Christopher Baines
2020-11-17 13:19 ` Linking to the data service Ludovic Courtès
2020-11-17 16:26 ` zimoun
2020-11-17 16:18 ` Data Services: use cases zimoun
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blfxm39q.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).