From: Alexandre Oliva <lxoliva@fsfla.org>
To: Leo Famulari <leo@famulari.name>
Cc: Vagrant Cascadian <vagrant@debian.org>, guix-devel <guix-devel@gnu.org>
Subject: Re: linux-libre source tarballs
Date: Thu, 06 May 2021 01:10:45 -0300 [thread overview]
Message-ID: <orzgx8cxiy.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <YJAvK3DE72FAP4EL@jasmine.lan> (Leo Famulari's message of "Mon, 3 May 2021 13:13:15 -0400")
On May 3, 2021, Leo Famulari <leo@famulari.name> wrote:
> 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.
I have heard about early format changes, but since Linux itself has used
git archive to generate tarballs on the fly, and published digital
signatures based on archives generated this way, I presume an
expectation that changes to the format won't be made without a very
compelling reason.
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
next prev parent reply other threads:[~2021-05-06 4:50 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
2021-05-06 4:10 ` Alexandre Oliva [this message]
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=orzgx8cxiy.fsf@lxoliva.fsfla.org \
--to=lxoliva@fsfla.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--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.