From: Jelle Licht <jlicht@fsfe.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 61454-close@debbugs.gnu.org
Subject: bug#61454: [PATCH 0/5] Expose upstream linux sources
Date: Sun, 12 Feb 2023 20:23:35 +0100 [thread overview]
Message-ID: <87r0uusn60.fsf@fsfe.org> (raw)
In-Reply-To: <87zg9iempe.fsf@nckx>
Hi Tobias,
Tobias Geerinckx-Rice <me@tobias.gr> writes:
> Hi Jelle!
>
> jlicht@fsfe.org 写道:
>> * Is this fundamentally going to be an issue with the FSDG?
>
> I can't think of a reading of the FSDG where it is not against
> both the letter and the spirit.
>
> Guix already ventures close to the edge; this would push us clean
> over.
Fair enough. I'll go ahead and assume that any "workaround" using public
bindings exposed by guix can be considered a bug, later to be addressed
by guix in order to prevent similar situations.
>> * This is the 'dumb' solution; alternatively, I was thinking of
>> introducing a
>> record to unify all the moving parts (the upstream sources,
>> the deblob
>> scripts) involved in building our linux-libre kernels.
>
> I'm not sure this will suit your purposes any better without
> amounting to the same thing.
It does, so never mind!
Thanks for your input,
- Jelle
prev parent reply other threads:[~2023-02-12 19:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 15:39 [bug#61454] [PATCH 0/5] Expose upstream linux sources jlicht
2023-02-12 15:42 ` [bug#61454] [PATCH 1/5] gnu: linux-libre 4.14: Expose upstream sources jlicht
2023-02-12 15:42 ` [bug#61454] [PATCH 2/5] gnu: linux-libre 4.19: " jlicht
2023-02-12 15:42 ` [bug#61454] [PATCH 3/5] gnu: linux-libre 5.10: " jlicht
2023-02-12 15:42 ` [bug#61454] [PATCH 4/5] gnu: linux-libre 5.15: " jlicht
2023-02-12 15:42 ` [bug#61454] [PATCH 5/5] gnu: linux-libre 6.1: " jlicht
2023-02-12 16:46 ` [bug#61454] [PATCH 0/5] Expose upstream linux sources Liliana Marie Prikler
2023-02-12 18:53 ` Tobias Geerinckx-Rice via Guix-patches via
2023-02-12 19:23 ` Jelle Licht [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=87r0uusn60.fsf@fsfe.org \
--to=jlicht@fsfe.org \
--cc=61454-close@debbugs.gnu.org \
--cc=me@tobias.gr \
/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.