From: Jonas Hahnfeld via "Developers list for Guile, the GNU extensibility library" <guile-devel@gnu.org>
To: guile-devel@gnu.org, bug-guile@gnu.org
Subject: Re: [PATCH] Build system fixes
Date: Wed, 20 Mar 2024 21:14:30 +0100 [thread overview]
Message-ID: <15e3f43c38653a0e791a624d8420e18468fdba22.camel@hahnjo.de> (raw)
In-Reply-To: <28cbafe86d959534413551b2fb3edec475e5be61.camel@hahnjo.de>
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
On Thu, 2024-02-22 at 22:14 +0100, Jonas Hahnfeld via Developers list
for Guile, the GNU extensibility library wrote:
> Dear Guile maintainers,
>
> please find attached two patches for changes that we have been carrying
> downstream in LilyPond so far: one fix to make a sed invocation fully
> portable, and a fix for cross-compilation in out-of-tree-builds.
ping...
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-03-20 20:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 21:14 [PATCH] Build system fixes Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2024-03-20 20:14 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library [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://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=15e3f43c38653a0e791a624d8420e18468fdba22.camel@hahnjo.de \
--to=guile-devel@gnu.org \
--cc=bug-guile@gnu.org \
--cc=hahnjo@hahnjo.de \
/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).