From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Raghav Gururajan <rg@raghavgururajan.name>
Cc: guix-devel@gnu.org
Subject: Re: Linux-Libre-LTS
Date: Tue, 03 Nov 2020 11:56:24 +0100 [thread overview]
Message-ID: <87k0v2hfon.fsf@nckx> (raw)
In-Reply-To: <07ff0907-e048-7213-5ca9-72a9f6c47c25@raghavgururajan.name>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
Hi Raghav,
Raghav Gururajan 写道：
> Sure! Yeah, making it default was the next thing in my mind.
Honestly no idea where I stand on that but I can bring the
popcorn.
>> We should use upstream[0] release names, though, not roll our
>> own
>> (+less clear) ones. So ‘-longterm’ instead of ‘-lts’.
>
> By upstream you mean linux-libre or linux?
Linux.
Linux-Libre don't develop a kernel nor backport/provide any of
said long-term ‘support’. They're ‘upstream’ of us in a trivial
way: we gratefully re-use their work.
> The linux-libre uses the name 'lts'.
Where? It's neither here[0] nor there[1]. I found it on blogs.
The name isn't that important; just don't change it for fun, and
‘longterm’ is what I'm used to hearing upstream.
Kind regards,
T G-R
[0]: https://www.fsfla.org/ikiwiki/selibre/linux-libre/
[1]:
http://linux-libre.fsfla.org/pub/linux-libre/releases/5.4.74-gnu/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-11-03 10:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 3:32 Linux-Libre-LTS Raghav Gururajan
2020-10-29 7:47 ` Linux-Libre-LTS Efraim Flashner
2020-11-03 3:41 ` Linux-Libre-LTS Raghav Gururajan
2020-12-24 3:54 ` Linux-Libre-LTS Raghav Gururajan
2020-12-26 18:09 ` Linux-Libre-LTS Efraim Flashner
2020-10-29 8:24 ` Linux-Libre-LTS Tobias Geerinckx-Rice
2020-10-29 14:16 ` Linux-Libre-LTS Leo Famulari
2020-11-03 3:44 ` Linux-Libre-LTS Raghav Gururajan
2020-11-03 10:56 ` Tobias Geerinckx-Rice [this message]
2020-11-03 19:54 ` Linux-Libre-LTS Raghav Gururajan
2020-11-03 20:06 ` Linux-Libre-LTS Tobias Geerinckx-Rice
2020-12-24 10:15 ` Linux-Libre-LTS Mark H Weaver
2020-12-24 10:37 ` Linux-Libre-LTS Jonathan Brielmaier
2020-12-25 2:24 ` Linux-Libre-LTS Mark H Weaver
2020-12-27 5:24 ` Linux-Libre-LTS Leo Famulari
2020-12-27 13:27 ` Linux-Libre-LTS Bengt Richter
2020-12-27 17:09 ` Linux-Libre-LTS Raghav Gururajan
2020-12-29 20:52 ` Linux-Libre-LTS Leo Famulari
2020-12-30 16:08 ` Linux-Libre-LTS Raghav Gururajan
2020-12-30 21:18 ` Linux-Libre-LTS Raghav Gururajan
2020-12-31 0:24 ` Linux-Libre-LTS Leo Famulari
2020-12-31 3:19 ` Linux-Libre-LTS Leo Famulari
2020-12-30 15:47 ` Linux-Libre-LTS Jonathan Brielmaier
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=87k0v2hfon.fsf@nckx \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=rg@raghavgururajan.name \
/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).