From: Guillaume Le Vaillant <glv@posteo.net>
To: Roman Scherer <roman@burningswell.com>
Cc: 73223-done@debbugs.gnu.org
Subject: bug#73223: [PATCH 1/2] gnu: Add sbcl-print-licenses.
Date: Sat, 14 Sep 2024 09:15:42 +0000 [thread overview]
Message-ID: <87ikuyy4sh.fsf@kitej> (raw)
In-Reply-To: <cdbc6e54f3ca49a29f15374aa296009ca175437b.1726221629.git.roman@burningswell.com> (Roman Scherer's message of "Fri, 13 Sep 2024 12:02:22 +0200")
[-- Attachment #1: Type: text/plain, Size: 105 bytes --]
Patches applied as 6d9a82a6fb8675441d63ae23b715952df13a845f and
following with some minor fixes.
Thanks.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
prev parent reply other threads:[~2024-09-14 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 10:02 [bug#73223] [PATCH 1/2] gnu: Add sbcl-print-licenses Roman Scherer
2024-09-13 10:02 ` [bug#73223] [PATCH 2/2] gnu: Add sbcl-s-base64 Roman Scherer
2024-09-14 9:15 ` Guillaume Le Vaillant [this message]
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=87ikuyy4sh.fsf@kitej \
--to=glv@posteo.net \
--cc=73223-done@debbugs.gnu.org \
--cc=roman@burningswell.com \
/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).