From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha@sourceware.org,
Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: glibc 2.27: less than two weeks till release
Date: Fri, 19 Jan 2018 08:54:00 -0000 [thread overview]
Message-ID: <1a5ecacf-af81-ef57-af6f-50edbffa700f@redhat.com> (raw)
In-Reply-To: <20180118175601.GC31922@altlinux.org>
On 01/18/2018 09:56 AM, Dmitry V. Levin wrote:
> ** C11 threads[6]
>
> This has been waiting for review for many weeks, last week Carlos said
> he will review this.
> It's unfortunate that we still have complicated all-arch patch series
> like this still pending review for 2.27.
My apologies for the delay, but basically metldown/spectre is probably
consuming *everyone's* free cycles on figuring out how the mitigation
will work. This has been the quietest freeze period I have ever seen
in my history working on the project.
Adhemerval, Would you be opposed to me reviewing this and committing
once the branch opens? Making it a feature of 2.28? I'd like to avoid
this commit so late in the freeze?
Cheers,
Carlos.
next prev parent reply other threads:[~2018-01-19 8:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 17:56 Dmitry V. Levin
2018-01-18 21:56 ` TODO: Alternative month names (was: Re: glibc 2.27: less than two weeks till release) Rafal Luzynski
2018-01-18 22:04 ` Zack Weinberg
2018-01-18 23:07 ` Rafal Luzynski
2018-01-19 8:51 ` TODO: Alternative month names Carlos O'Donell
2018-01-19 10:41 ` Rafal Luzynski
2018-01-19 8:54 ` Carlos O'Donell [this message]
2018-01-21 22:01 ` glibc 2.27: less than two weeks till release Romain Naour
2018-01-22 11:11 ` Szabolcs Nagy
2018-01-22 11:53 ` Adhemerval Zanella
2018-01-22 12:08 ` Szabolcs Nagy
2018-01-22 15:49 ` Joseph Myers
2018-01-22 16:00 ` Florian Weimer
2018-01-22 15:45 ` Joseph Myers
2018-01-24 21:57 ` Romain Naour
2018-01-24 22:02 ` Joseph Myers
2018-01-28 17:35 ` Romain Naour
2018-01-29 20:30 ` Joseph Myers
2018-01-30 0:21 ` Romain Naour
2018-01-30 1:01 ` Joseph Myers
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=1a5ecacf-af81-ef57-af6f-50edbffa700f@redhat.com \
--to=carlos@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--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).