From: Mark Wielaard <mark@klomp.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH] Add helper function for basename
Date: Thu, 14 Dec 2023 20:22:19 +0100 [thread overview]
Message-ID: <20231214192219.GB12145@gnu.wildebeest.org> (raw)
In-Reply-To: <CAMKF1srsbanq6T-Djnhz4UGKOhqGMsyL2eNSwgEBkDs0_B63wQ@mail.gmail.com>
Hi Khem,
On Thu, Dec 14, 2023 at 10:15:00AM -0800, Khem Raj wrote:
> Overall, this looks a good improvement on top of my patch so good to go.
> I will also try it in my local distro builds and see how it goes.
Thanks. I didn't actually test it against musl. So if you could and
report whether or not it works as intended that would be really
appreciated.
Cheers,
Mark
next prev parent reply other threads:[~2023-12-14 19:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 20:20 Khem Raj
2023-12-12 13:18 ` Mark Wielaard
2023-12-12 17:16 ` Khem Raj
2023-12-13 15:10 ` Mark Wielaard
2023-12-13 16:29 ` Khem Raj
2023-12-13 22:33 ` Mark Wielaard
2023-12-14 18:07 ` Mark Wielaard
2023-12-14 18:15 ` Khem Raj
2023-12-14 19:22 ` Mark Wielaard [this message]
2023-12-14 19:28 ` Khem Raj
2023-12-20 16:43 ` Khem Raj
2023-12-21 1:02 ` Mark Wielaard
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=20231214192219.GB12145@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=raj.khem@gmail.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.
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).