From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org, Xi Ruoyao <xry111@xry111.site>
Subject: Re: Freeze for the upcoming glibc 2.39 release - status
Date: Fri, 12 Jan 2024 14:25:16 +0100 [thread overview]
Message-ID: <2861500.Y6S9NjorxK@pinacolada> (raw)
In-Reply-To: <9245579961f26e68e095a6f25f86003e1af49e43.camel@xry111.site>
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
Am Freitag, 12. Januar 2024, 14:14:47 CET schrieb Xi Ruoyao:
> 在 2024-01-12星期五的 07:56 -0300，Adhemerval Zanella Netto写道：
> > > [PATCH v2] Make __getrandom_nocancel set errno and add a _nostatus version
> > > https://patchwork.sourceware.org/project/glibc/list/?series=29130
> > > R-B Adhemerval
> > > bug fix - should go in now?
> > >
> >
> > Yes, I think it would be good.
>
> Note that I don't have a write access to glibc.git, so relying on you
> guys to push it if considered OK :).
>
No problem and thanks for the hint. :) Pushed.
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2024-01-12 13:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 13:18 Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release Andreas K. Huettel
2024-01-02 9:14 ` Florian Weimer
2024-01-02 9:21 ` autoconf 2.72 ? (Re: Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release) Andreas K. Huettel
2024-01-02 10:27 ` Florian Weimer
2024-01-02 17:35 ` Paul Eggert
2024-01-02 19:17 ` [PATCH, test conversion, RFC] Convert to autoconf 2.72 (no patches) Andreas K. Hüttel
2024-01-02 21:30 ` Florian Weimer
2024-01-03 4:13 ` Paul Eggert
2024-01-10 18:37 ` Carlos O'Donell
2024-01-02 14:39 ` Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release Adhemerval Zanella Netto
2024-01-06 12:27 ` Andreas K. Huettel
2024-01-08 12:54 ` Adhemerval Zanella Netto
2024-01-02 15:22 ` H.J. Lu
2024-01-06 22:29 ` Andreas K. Huettel
2024-01-03 21:57 ` enh
2024-01-10 18:38 ` Carlos O'Donell
2024-01-10 20:33 ` Jeff Law
2024-01-11 1:10 ` Palmer Dabbelt
2024-01-12 6:13 ` Palmer Dabbelt
2024-01-11 22:24 ` Freeze for the upcoming glibc 2.39 release - status Andreas K. Huettel
2024-01-12 10:56 ` Adhemerval Zanella Netto
2024-01-12 13:14 ` Xi Ruoyao
2024-01-12 13:25 ` Andreas K. Huettel [this message]
2024-01-12 14:23 ` Andreas K. Huettel
2024-01-12 17:19 ` Carlos O'Donell
2024-01-12 17:34 ` Palmer Dabbelt
2024-01-12 18:10 ` Adhemerval Zanella Netto
2024-01-12 22:10 ` Palmer Dabbelt
2024-01-12 22:21 ` Freeze for the upcoming glibc 2.39 release - status (2) Andreas K. Huettel
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=2861500.Y6S9NjorxK@pinacolada \
--to=dilfridge@gentoo.org \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=xry111@xry111.site \
/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).