public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zackw@panix.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] New configure option --disable-crypt.
Date: Mon, 23 Apr 2018 15:29:00 -0000	[thread overview]
Message-ID: <CAKCAbMjz90CPj2XTRKppbHQqXp=xRzg3a2KMAyBLAHk5int1DQ@mail.gmail.com> (raw)
In-Reply-To: <877ep4i6xm.fsf@linux-m68k.org>

On Wed, Apr 18, 2018 at 4:41 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> On Apr 18 2018, Zack Weinberg <zackw@panix.com> wrote:
>
>> diff --git a/NEWS b/NEWS
>> index 92c9b14220..b530124dae 100644
>> --- a/NEWS
>> +++ b/NEWS
>> @@ -31,7 +31,7 @@ Deprecated and removed features, and other changes affecting compatibility:
>>     installed.  Software that was using either header should be updated to
>>     use standard <stdio.h> interfaces instead.
>>
>> - * The stdio.h functions 'getc' and 'putc' are no longer defined as macros.
>> + * The stdio functions 'getc' and 'putc' are no longer defined as macros.
>>     This was never required by the C standard, and the macros just expanded
>>     to call alternative names for the same functions.  If you hoped getc and
>>     putc would provide performance improvements over fgetc and fputc, instead
>
> This is unrelated.

I split this and pushed it separately.

zw

  reply	other threads:[~2018-04-23 15:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-18 18:34 Zack Weinberg
2018-04-18 20:41 ` Andreas Schwab
2018-04-23 15:29   ` Zack Weinberg [this message]
2018-04-18 21:05 ` Rical Jasan
2018-04-23 15:22   ` Zack Weinberg

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='CAKCAbMjz90CPj2XTRKppbHQqXp=xRzg3a2KMAyBLAHk5int1DQ@mail.gmail.com' \
    --to=zackw@panix.com \
    --cc=libc-alpha@sourceware.org \
    --cc=schwab@linux-m68k.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).