From: Jason Self <jself@gnu.org>
To: guix-devel@gnu.org
Subject: Re: Linux-libre source code will be taken offline
Date: Tue, 28 Sep 2021 07:30:23 -0700 [thread overview]
Message-ID: <E1mVE8O-0002XT-JQ@eggs.gnu.org> (raw)
In-Reply-To: 86czotccpj.fsf@gmail.com
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
Granted that old/gen7 is not currently a valid URL but we can know
that, 5 or 10 years from now, when Linux-libre has moved on to the 8th,
9th or even 10th generation, the 7th generation scripts will exist
there. If Guix can begin checking those additional locations now then,
in the future once the current Guix version becomes an old version,
hopefully it can transparently handle that transition without issue. Or
just use git. :)
Even this method is just a band-aid though and has a different set of
challenges for the long-term. I'd be happy to discuss that with whoever
is interested.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-09-28 14:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 18:17 Linux-libre source code will be taken offline Leo Famulari
2021-09-04 20:32 ` Jason Self
2021-09-06 17:36 ` Leo Famulari
2021-09-27 22:30 ` Mark H Weaver
2021-09-27 23:17 ` Vagrant Cascadian
2021-09-28 13:05 ` Ludovic Courtès
2021-09-27 23:30 ` Leo Famulari
2021-09-28 0:13 ` zimoun
2021-09-28 0:17 ` zimoun
2021-09-28 0:46 ` Jason Self
2021-09-28 8:43 ` zimoun
2021-09-28 14:02 ` Jason Self
2021-09-28 14:30 ` Jason Self [this message]
2021-09-28 17:11 ` zimoun
2021-09-28 17:52 ` Jason Self
2021-09-29 8:50 ` zimoun
2021-10-08 1:58 ` Maxim Cournoyer
2021-10-11 8:43 ` zimoun
2021-09-08 22:00 ` Ludovic Courtès
2021-09-08 23:46 ` Why linux-libre source code is not in sources.json zimoun
2021-09-09 7:37 ` zimoun
2021-09-09 9:50 ` Maxime Devos
2021-09-09 17:18 ` zimoun
2021-09-11 0:22 ` Linux-libre source code via SWH sources.json 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=E1mVE8O-0002XT-JQ@eggs.gnu.org \
--to=jself@gnu.org \
--cc=guix-devel@gnu.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.
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).