all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, 75137@debbugs.gnu.org
Cc: "Christopher Baines" <guix@cbaines.net>,
	"Ludovic Courtès" <ludo@gnu.org>,
	"Tobias Geerinckx-Rice" <me@tobias.gr>,
	"Josselin Poiret" <dev@jpoiret.xyz>,
	"Mathieu Othacehe" <othacehe@gnu.org>
Subject: [bug#75137] [PATCH 1/4] upstream: Switch to SRFI-71.
Date: Mon, 06 Jan 2025 11:57:03 +0100	[thread overview]
Message-ID: <87zfk4xla8.fsf@gmail.com> (raw)
In-Reply-To: <1878ae44b216f1f8b92efb19a7a67b435af23c90.1735296761.git.ludo@gnu.org>

Hi,

On Fri, 27 Dec 2024 at 11:56, Ludovic Courtès <ludo@gnu.org> wrote:

> * guix/upstream.scm (download-tarball, package-update/url-fetch): Use
> SRFI-71 instead of SRFI-11.

Out of curiosity, could you explain why SRFI-71 is preferred over
SRFI-11?  And is it only for this specific case?  Or something that
might be better for all the code base?

Cheers,
simon




  reply	other threads:[~2025-01-06 17:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-27 10:55 [bug#75137] [PATCH 0/4] 'package-with-upstream-version' can preserve archive type Ludovic Courtès
2024-12-27 10:56 ` [bug#75137] [PATCH 1/4] upstream: Switch to SRFI-71 Ludovic Courtès
2025-01-06 10:57   ` Simon Tournier [this message]
2025-01-08  9:59     ` Ludovic Courtès
2025-01-09 11:11       ` Simon Tournier
2024-12-27 10:56 ` [bug#75137] [PATCH 2/4] upstream: Extract ‘preferred-upstream-source-url’ Ludovic Courtès
2024-12-27 10:56 ` [bug#75137] [PATCH 3/4] upstream: Define ‘preferred-upstream-source’ Ludovic Courtès
2024-12-27 10:56 ` [bug#75137] [PATCH 4/4] transformations: ‘package-with-upstream-version’ can preserve archive type Ludovic Courtès
2025-01-06 11:09 ` [bug#75137] [PATCH 0/4] 'package-with-upstream-version' " Simon Tournier
2025-01-08 23:26   ` bug#75137: " Ludovic Courtès

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=87zfk4xla8.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=75137@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=guix@cbaines.net \
    --cc=ludo@gnu.org \
    --cc=me@tobias.gr \
    --cc=othacehe@gnu.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.