unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Mark H Weaver <mhw@netris.org>
Cc: Vagrant Cascadian <vagrant@debian.org>, 42789@debbugs.gnu.org
Subject: bug#42789: Linux-libre 5.8 and beyond
Date: Tue, 11 Aug 2020 18:46:01 -0400	[thread overview]
Message-ID: <20200811224601.GA31177@jasmine.lan> (raw)
In-Reply-To: <871rkdj13e.fsf@netris.org>

[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]

On Mon, Aug 10, 2020 at 11:46:34PM -0400, Mark H Weaver wrote:
> If we're going to prefix "linux-libre-" to the name, which I agree is a
> good idea, maybe we should add the same prefix to the other 'deblob'
> script, for consistency.  Also for consistency, I think the version
> number should be at the end, after "deblob-check", as is the case for
> the other deblob script.
>
> There's also the question of whether the micro version number should be
> included in the file name.  In practice, these deblob scripts almost
> never change from one micro version to the next.  Also, I suspect
> (although I've not yet confirmed it) that these deblob scripts likely
> work for older kernels in the same stable series.
> 
> For those reasons, at present the micro version number appears only in
> the URLs, and not in either the file names or in the version number as
> recorded in the first element of the triplet returned by
> 'linux-libre-deblob-scripts'.  I'd personally be inclined to keep it
> that way, although I don't feel strongly about it.

Good ideas. I've taken them into account on my local branch while I test
building the final tarballs. I'll push to the kernel-updates branch once
I am satisfied with the result.

Thanks for your feedback!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-08-11 22:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87lfio4hs4.fsf@netris.org>
     [not found] ` <87v9hscwm7.fsf@ponder>
     [not found]   ` <877du7adz6.fsf@ponder>
     [not found]     ` <87imdr4g60.fsf@netris.org>
2020-08-10  1:59       ` bug#42789: Linux-libre 5.8 and beyond Leo Famulari
2020-08-10 17:16         ` bug#42789: Linux-libre 'deblob-check' file-names do not include a version number Leo Famulari
2020-08-11  3:46         ` bug#42789: Linux-libre 5.8 and beyond Mark H Weaver
2020-08-11 22:46           ` Leo Famulari [this message]
2020-08-12  3:24             ` Leo Famulari
2020-08-12 21:34         ` Mark H Weaver
2020-08-21 22:02           ` Leo Famulari

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=20200811224601.GA31177@jasmine.lan \
    --to=leo@famulari.name \
    --cc=42789@debbugs.gnu.org \
    --cc=mhw@netris.org \
    --cc=vagrant@debian.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).