From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 41908-done@debbugs.gnu.org
Subject: bug#41908: guix time-machine fails; XXXX is not related to introductory commit of channel 'guix'
Date: Tue, 23 Jun 2020 10:53:46 +0200 [thread overview]
Message-ID: <87blla40yt.fsf@gnu.org> (raw)
In-Reply-To: <86d05qrx5a.fsf@gmail.com> (zimoun's message of "Tue, 23 Jun 2020 10:42:25 +0200")
zimoun <zimon.toutoune@gmail.com> skribis:
> Just to be sure to understand:
>
> 1- * 41a2d6a8b9 (newer)
> 2- * e70e097882 (between)
> 3- * 36640207c9 (older)
> 4- * xxxxxxxxxx (first authenticated commit)
>
> From a fresh cache,
>
> a) if #2 is authenticated, because it is descendant of #4, it is stored
> and all the commits between (closure), i.e., #3 should be considered as
> authenticated.
>
> b) then if #1 is authenticated, because it is a descendant of the last
> authenticated i.e. #2, it is stored in the cache.
>
> c) now let try #3. It is considered authenticated because in the closure
> of #4 and #2.
>
> Yes it makes sense. All is good. :-)
Yup, looks correct. :-)
> (And the assumption is: if Guix does not raise then it means that the
> commit is authenticated.)
Exactly. I know it’s disappointing, but it’s one of these features
that’s pretty much invisible until you run into troubles.
Ludo’.
prev parent reply other threads:[~2020-06-23 8:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 9:27 bug#41908: guix time-machine fails; XXXX is not related to introductory commit of channel 'guix' Jan Nieuwenhuizen
2020-06-18 22:29 ` zimoun
2020-06-18 23:02 ` zimoun
2020-06-19 21:17 ` Ludovic Courtès
2020-06-19 23:22 ` zimoun
2020-06-20 10:40 ` Ludovic Courtès
2020-06-21 16:17 ` zimoun
2020-06-22 8:01 ` Ludovic Courtès
2020-06-20 13:58 ` Marius Bakke
2020-06-21 15:43 ` Ludovic Courtès
2020-06-21 16:18 ` zimoun
2020-06-22 8:54 ` zimoun
2020-06-23 7:35 ` Ludovic Courtès
2020-06-23 8:42 ` zimoun
2020-06-23 8:53 ` Ludovic Courtès [this message]
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=87blla40yt.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=41908-done@debbugs.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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.