unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: GLIBC Devel <libc-alpha@sourceware.org>
Subject: Re: glibc 2.29 - Winter is coming...
Date: Wed, 02 Jan 2019 11:59:48 +0100	[thread overview]
Message-ID: <87r2dv495n.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <833db514-f25e-0c41-bf06-b8cc9272f1c2@gotplt.org> (Siddhesh Poyarekar's message of "Wed, 2 Jan 2019 15:58:04 +0530")

* Siddhesh Poyarekar:

> I have reviewed all original release blockers, including a couple of
> additional ones that got added later but I couldn't get to all of
> them. As of now, the pending blockers do not look suitable for
> inclusion at this stage and so will be deferred to 2.30 development.

I support this decision, with the possible exception of “preserve
sprintf(buf, "%s", buf) behaviour” and “posix: Clear close-on-exec for
posix_spawn adddup2 (BZ#23640)”.

Thanks,
Florian

  reply	other threads:[~2019-01-02 10:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-02 10:28 glibc 2.29 - Winter is coming Siddhesh Poyarekar
2019-01-02 10:59 ` Florian Weimer [this message]
2019-01-02 11:29   ` Siddhesh Poyarekar
2019-01-02 11:52     ` Rafal Luzynski
2019-01-02 18:24       ` Siddhesh Poyarekar
2019-01-03  0:20         ` Rafal Luzynski
2019-01-03 14:32           ` Carlos O'Donell
2019-01-03 20:58             ` Joseph Myers
2019-01-04 21:25               ` Carlos O'Donell
2019-01-07 18:59               ` Florian Weimer
2019-01-02 13:11     ` Gabriel F. T. Gomes
2019-01-02 13:16       ` Florian Weimer
2019-01-02 13:47         ` Siddhesh Poyarekar
2019-01-02 16:02           ` Gabriel F. T. Gomes
2019-01-08 13:33 ` Szabolcs Nagy
2019-01-08 14:16   ` Carlos O'Donell
2019-01-08 14:21     ` Szabolcs Nagy
2019-01-08 16:50       ` Carlos O'Donell
2019-01-09 10:50         ` Ramana Radhakrishnan
2019-01-09 16:03           ` Carlos O'Donell
     [not found]             ` <BL0PR01MB4593D75E9376CC15EE8CA24AF7990@BL0PR01MB4593.prod.exchangelabs.com>
2019-01-23 14:07               ` Carlos O'Donell
2019-01-09  5:48       ` Siddhesh Poyarekar

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r2dv495n.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@gotplt.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).