From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Release progress, week 10
Date: Mon, 19 Dec 2022 22:34:59 +0100 [thread overview]
Message-ID: <87zgbjaxh8.fsf@gnu.org> (raw)
In-Reply-To: <86y1r3y9dd.fsf@gmail.com> (zimoun's message of "Mon, 19 Dec 2022 11:29:34 +0100")
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
> On Sun, 18 Dec 2022 at 16:13, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> I wrote a couple of paragraphs about this and other things yesterday
>> (tried to keep it relatively short). Let me know if you think
>> anything’s missing.
>
> All appears to me good. You do not mention that the coverage for
> git-fetch is about ~98% and that Disarchive is very important because
> the main source of origins is url-fetch, hence the total of 75%.
>
> I would add at the end of the first paragraph something like:
>
> [...]
> Software Heritage as a fallback, with version 1.4.0 **the source code of
> Guix channels is automatically fetched from Software Heritage** if its
> original URL has become unreachable. As of the “[Preservation of Guix
> Report](https://ngyro.com/pog-reports/latest/)” published in January
> 2022, more than 98% of the packages directly referring to Git
> repositories are now fully archived in Software Heritage.
Sorry this came in too late, but we can have it in the announcement for
hpc.guix.info (tomorrow I guess?).
Thanks,
Ludo’.
prev parent reply other threads:[~2022-12-19 21:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 16:38 Release progress, week 10 Ludovic Courtès
2022-12-15 21:26 ` cirrus (was Re: Release progress, week 10) pelzflorian (Florian Pelz)
2022-12-17 19:18 ` pelzflorian (Florian Pelz)
2022-12-18 15:11 ` Ludovic Courtès
2022-12-18 16:27 ` pelzflorian (Florian Pelz)
2022-12-17 12:11 ` Release progress, week 10 zimoun
2022-12-18 15:13 ` Ludovic Courtès
2022-12-19 10:29 ` zimoun
2022-12-19 21:34 ` 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=87zgbjaxh8.fsf@gnu.org \
--to=ludo@gnu.org \
--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 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.