From: Andreas Schwab <schwab@suse.de>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] Assume that _IO_MTSAFE_IO is always defined in libio/stdfiles.c
Date: Tue, 19 Jun 2018 09:31:00 -0000 [thread overview]
Message-ID: <mvmr2l39l7s.fsf@suse.de> (raw)
In-Reply-To: <871sd36s63.fsf@mid.deneb.enyo.de> (Florian Weimer's message of "Tue, 19 Jun 2018 11:29:08 +0200")
On Jun 19 2018, Florian Weimer <fw@deneb.enyo.de> wrote:
> * Andreas Schwab:
>
>> On Jun 19 2018, Florian Weimer <fw@deneb.enyo.de> wrote:
>>
>>> * Andreas Schwab:
>>>
>>>> On Jun 19 2018, Florian Weimer <fw@deneb.enyo.de> wrote:
>>>>
>>>>> * libio/stdfiles.c (DEF_STDFILE): Assume that _IO_MTSAFE_IO is
>>>>> always defined.
>>>>
>>>> Why only here?
>>>
>>> _IO_MTSAFE_IO has a bit of a checkered history. Previous attempts at
>>> removal failed when they encountered resistance in the form of parts
>>> of the library that were *not* compiled with _IO_MTSAFE_IO.
>>>
>>> I need to change DEF_STDFILE to fix bug 23313.
>>
>> That bug isn't even referenced here.
>
> Yes, it's an independent change.
I don't understand. Either it fixes a bug or it is pointless.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2018-06-19 9:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 9:03 Florian Weimer
2018-06-19 9:14 ` Andreas Schwab
2018-06-19 9:17 ` Florian Weimer
2018-06-19 9:27 ` Andreas Schwab
2018-06-19 9:29 ` Florian Weimer
2018-06-19 9:31 ` Andreas Schwab [this message]
2018-06-19 9:57 ` Florian Weimer
2018-06-19 10:16 ` Andreas Schwab
2018-06-19 10:18 ` Florian Weimer
2018-06-19 10:30 ` Andreas Schwab
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=mvmr2l39l7s.fsf@suse.de \
--to=schwab@suse.de \
--cc=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.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).