From: Florian Weimer <fweimer@redhat.com>
To: Ben Hutchings <ben.hutchings@codethink.co.uk>,
Rical Jasan <ricaljasan@pacific.net>
Cc: libc-alpha <libc-alpha@sourceware.org>,
Carlos O'Donell <carlos@redhat.com>
Subject: Re: [RFC] DT_WHT
Date: Mon, 05 Mar 2018 09:47:00 -0000 [thread overview]
Message-ID: <ee5a5820-cd01-03f8-4085-13ef81d97a96@redhat.com> (raw)
In-Reply-To: <1520214640.2786.62.camel@codethink.co.uk>
On 03/05/2018 02:50 AM, Ben Hutchings wrote:
> I have no opinion on that code, but it sounded like you proposed to
> remove the macro definition too. I wanted to point out that the macro
> is meaningful and may be useful to applications.
Useful in what sense? What are its semantics?
Thanks,
Florian
next prev parent reply other threads:[~2018-03-05 9:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 10:49 Rical Jasan
2018-02-22 7:03 ` Carlos O'Donell
2018-03-01 16:24 ` Ben Hutchings
2018-03-01 23:02 ` Rical Jasan
2018-03-05 1:50 ` Ben Hutchings
2018-03-05 9:47 ` Florian Weimer [this message]
2018-03-05 16:21 ` Ben Hutchings
2018-03-06 11:28 ` Florian Weimer
2018-03-05 10:49 ` Rical Jasan
2018-03-05 16:23 ` Ben Hutchings
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=ee5a5820-cd01-03f8-4085-13ef81d97a96@redhat.com \
--to=fweimer@redhat.com \
--cc=ben.hutchings@codethink.co.uk \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=ricaljasan@pacific.net \
/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).