From: Florian Weimer <fw@deneb.enyo.de>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: GLIBC Devel <libc-alpha@sourceware.org>
Subject: Re: 2.31: < 2 weeks to go
Date: Mon, 30 Dec 2019 16:00:08 +0100 [thread overview]
Message-ID: <87imlxq2o7.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <4c5a8252-a985-bf71-275a-1f00c40b2949@gotplt.org> (Siddhesh Poyarekar's message of "Mon, 30 Dec 2019 17:50:56 +0530")
* Siddhesh Poyarekar:
> Florian, your syscall patchset is good to go with fixups to 1/5; would
> you be able to post an updated set in the next day or two?
I hope so. I have some trouble typing, so there hasn't been any
progress yet.
prev parent reply other threads:[~2019-12-30 15:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 3:35 2.31: < 2 weeks to go Siddhesh Poyarekar
2019-12-20 3:56 ` Carlos O'Donell
2019-12-20 9:45 ` Arjun Shankar
2019-12-24 14:36 ` Chung-Lin Tang
2019-12-27 12:39 ` Carlos O'Donell
2020-01-07 19:29 ` Carlos O'Donell
2019-12-20 14:30 ` Florian Weimer
2019-12-22 17:38 ` Siddhesh Poyarekar
2019-12-22 18:59 ` Joseph Myers
2019-12-30 12:20 ` Siddhesh Poyarekar
2019-12-30 15:00 ` Florian Weimer [this message]
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=87imlxq2o7.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--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).