From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 46258@debbugs.gnu.org, 54485@debbugs.gnu.org
Subject: bug#46258: bug#54485: [PATCH] gnu: Add guile-with-openat.
Date: Thu, 24 Mar 2022 12:55:41 +0100 [thread overview]
Message-ID: <c1bc08a29b8c836ce6098e28fb0c01c2587bc013.camel@telenet.be> (raw)
In-Reply-To: <87czibd1j3.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
Ludovic Courtès schreef op do 24-03-2022 om 12:37 [+0100]:
> Instead, I would prefer to actually review and apply the patches
> upstream. I’ve been meaning to do that, really, but it requires a chunk
> of time and focus, which keeps leading me to postpone.
OK. I can relate, w.r.t. the IPFS substitution patches.
> Is the latest patch set on guile-devel? It’s not mentioned at
> <https://issues.guix.gnu.org/46258>.
It's at <https://lists.gnu.org/archive/html/guile-devel/2021-11/msg00005.html>.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
parent reply other threads:[~2022-03-24 11:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87czibd1j3.fsf@gnu.org>]
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c1bc08a29b8c836ce6098e28fb0c01c2587bc013.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=46258@debbugs.gnu.org \
--cc=54485@debbugs.gnu.org \
--cc=ludo@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.
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).