public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zackw@panix.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH 2/6] Committed: Remove __need macros from signal.h.
Date: Tue, 23 May 2017 02:33:00 -0000	[thread overview]
Message-ID: <CAKCAbMj5M0zFZyn4Myf5af8JX8gyr+Yrmzhb9B8iE+8YQLT9Ow@mail.gmail.com> (raw)
In-Reply-To: <CAKCAbMh=Y28+TmEngoFSM+PZABx+cmadyRo_nEg18bH_s9AFmQ@mail.gmail.com>

On Mon, May 22, 2017 at 7:59 AM, Zack Weinberg <zackw@panix.com> wrote:
> I'm testing this patch now.  It will take all day to test thoroughly.
> I apologize for the inconvenience.

This has been checked in now.

  reply	other threads:[~2017-05-23  2:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-20 23:18 [PATCH 0/6] Elimination of __need macros, round 3(?) Zack Weinberg
2017-05-20 23:18 ` [PATCH 4/6] Remove __need macros from stdio.h and wchar.h Zack Weinberg
2017-05-20 23:18 ` [PATCH 5/6] Remove __need_IOV_MAX and __need_FOPEN_MAX Zack Weinberg
2017-05-20 23:18 ` [PATCH 2/6] Committed: Remove __need macros from signal.h Zack Weinberg
2017-05-21  7:19   ` Andreas Schwab
2017-05-21 13:55     ` Zack Weinberg
2017-05-22 11:18   ` Joseph Myers
2017-05-22 11:25     ` Joseph Myers
2017-05-22 11:59       ` Zack Weinberg
2017-05-23  2:33         ` Zack Weinberg [this message]
2017-05-20 23:18 ` [PATCH 3/6] Remove __need macros from errno.h (__need_Emath, __need_error_t) Zack Weinberg
2017-05-20 23:18 ` [PATCH 6/6] Remove __need_schedparam and __cpu_set_t_defined Zack Weinberg
2017-05-20 23:18 ` [PATCH 1/6] Committed: Remove __need_list_t and __need_res_state Zack Weinberg
2017-05-23 17:42 ` [PATCH 0/6] Elimination of __need macros, round 3(?) Chris Metcalf

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=CAKCAbMj5M0zFZyn4Myf5af8JX8gyr+Yrmzhb9B8iE+8YQLT9Ow@mail.gmail.com \
    --to=zackw@panix.com \
    --cc=joseph@codesourcery.com \
    --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).