From: "Ludovic Courtès" <ludo@gnu.org>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 37049-done@debbugs.gnu.org
Subject: bug#37049: [PATCH] gnu: txr: Update to 223.
Date: Fri, 16 Aug 2019 22:50:23 +0200 [thread overview]
Message-ID: <87v9uwg7hs.fsf@gnu.org> (raw)
In-Reply-To: <20190816091956.17920-1-glv@posteo.net> (Guillaume Le Vaillant's message of "Fri, 16 Aug 2019 11:19:56 +0200")
Hi,
Guillaume Le Vaillant <glv@posteo.net> skribis:
> * gnu/packages/lisp.scm (txr): Update to 223.
Applied!
I noticed that the tarball is a cgit snapshot, which is not guaranteed
to remain bit-identical as cgit changes. Could you, in a future patch,
arrange so that it is fetched over Git, using ‘git-fetch’?
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-08-16 20:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 9:19 [bug#37049] [PATCH] gnu: txr: Update to 223 Guillaume Le Vaillant
2019-08-16 20:50 ` Ludovic Courtès [this message]
2019-08-16 20:55 ` Guillaume Le Vaillant
2019-08-16 21:01 ` Guillaume Le Vaillant
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=87v9uwg7hs.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=37049-done@debbugs.gnu.org \
--cc=glv@posteo.net \
/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).