From: Leo Famulari <leo@famulari.name>
To: Alexandre Oliva <lxoliva@fsfla.org>
Cc: Vagrant Cascadian <vagrant@debian.org>, guix-devel <guix-devel@gnu.org>
Subject: Re: linux-libre source tarballs
Date: Mon, 3 May 2021 13:13:15 -0400 [thread overview]
Message-ID: <YJAvK3DE72FAP4EL@jasmine.lan> (raw)
In-Reply-To: <orim3zixet.fsf@lxoliva.fsfla.org>
On Mon, May 03, 2021 at 01:39:54PM -0300, Alexandre Oliva wrote:
> You don't have to clone anything. If all you want is a tarball, use
> 'git archive --remote'.
Thanks, I didn't know about this feature. Is the tarball generation
"stable" across Git releases? Or is it subject to change? We had this
issue with Git archive creation in the past.
> Is it correct to assume that they have never reached you? Would you
> like to have a look and let me know whether they make sense to you? I'd
> be glad to dig them up and share them with you, if so, and to take your
> feedback towards making them available to the public at large.
Personally, as a non-maintainer, I'd prefer to preserve the status quo
of our linux-libre packaging. If the maintainers decide that it should
be changed, I'll follow their decision.
next prev parent reply other threads:[~2021-05-03 17:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 1:45 linux-libre source tarballs Vagrant Cascadian
2021-05-02 2:45 ` Leo Famulari
2021-05-02 4:42 ` Leo Famulari
2021-05-02 21:08 ` Ludovic Courtès
2021-05-02 22:26 ` Leo Famulari
2021-05-02 22:38 ` Leo Famulari
2021-05-03 15:44 ` linux-libre source tarballs (disable "deblob-check"?) Leo Famulari
2021-05-03 16:39 ` linux-libre source tarballs Alexandre Oliva
2021-05-03 17:13 ` Leo Famulari [this message]
2021-05-06 4:10 ` Alexandre Oliva
2021-05-06 21:23 ` Leo Famulari
2021-05-06 20:30 ` Maxim Cournoyer
2021-05-09 3:27 ` Alexandre Oliva
2021-05-30 4:50 ` Vagrant Cascadian
2021-05-31 3:42 ` Leo Famulari
2021-05-31 19:57 ` Mathieu Othacehe
2021-08-01 20:45 ` source tarballs potentially built for each derivation Vagrant Cascadian
2021-08-01 21:04 ` Vagrant Cascadian
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=YJAvK3DE72FAP4EL@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=lxoliva@fsfla.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 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.