From: Jens Axboe <[email protected]>
To: Arthur Williams <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH] Fix portability issues in configure script
Date: Fri, 26 Apr 2024 08:30:07 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Thu, 25 Apr 2024 23:31:50 -0700, Arthur Williams wrote:
> The configure script failed on my setup because of the invalid printf
> directive "%" and for use of the unportable "echo -e". These have been
> replaced with more portable options.
>
>
Applied, thanks!
[1/1] Fix portability issues in configure script
commit: 380d12d0f5d68be09ccc6151ccca3e15857b16fa
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-04-26 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 17:27 [PATCH] Fix portability issues in configure script Arthur Williams
2024-04-09 17:37 ` Ammar Faizi
2024-04-26 6:31 ` Arthur Williams
2024-04-26 14:30 ` Jens Axboe [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=171414180700.215689.14972621787937962088.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
/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