From: Samuel Thibault <samuel.thibault@aquilenet.fr>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [STATS] Auto-update patchwork for committed patches
Date: Wed, 17 May 2023 19:14:20 +0200 [thread overview]
Message-ID: <20230517171420.iy5zmgai76iagikd@begin> (raw)
In-Reply-To: <ca01ca16-189b-51e3-68fa-e159491f73a1@gotplt.org>
Siddhesh Poyarekar, le mer. 17 mai 2023 11:30:37 -0400, a ecrit:
> 4571fb8fe64644c79d91a8f76c148a05b7088ea8 Update hurd/intr-msg.c to be more
> portable: MISSING
> 3f433cb895dee51dee57cb487bc33b1425fa7ef6 Update sysdeps/mach/hurd/ioctl.c to
> make it more portable: MISSING
> a26238d3ca21fda6d7d41b4d56541fcf4546fbe7 Enable new device_open_new RPC in
> libmachuser.: MISSING
> 3ca9f43d1007956251130ee5a59abb63bff8a6b6 Stop checking if MiG supports
> retcode.: MISSING
> 114f1b7881e63e2b4e5d0e9a9e4fb142b9cd886c hurd: Fix computing user stack
> pointer: MISSING
> e333759f7752593a69a8f9920a247ed3878fafef hurd: Fix sc_i386_thread_state
> layout: MISSING
> ce96593c882b393461084048533120e9c1e9d328 hurd: Align signal stack pointer
> after allocating stackframe: MISSING
> ff0f87632a74a369a2b992f4436ae406065a4012 hurd: Fix aligning signal stack
> pointer: MISSING
I don't remember changing anything in those?
For instance
> 4571fb8fe64644c79d91a8f76c148a05b7088ea8 Update hurd/intr-msg.c to be more
> portable: MISSING
reached the mailing list on
https://sourceware.org/pipermail/libc-alpha/2023-May/147836.html
or perhaps since I had already marked the patch as commited and
archived, your script didn't find it?
> d6c72f976c61d3c1465699f2bcad77e62bafe61d hurd: rule out some mach headers
> when generating errno.h: MISSING
I probably forgot to send the mail for this one, now done.
Samuel
next prev parent reply other threads:[~2023-05-17 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 15:30 Siddhesh Poyarekar
2023-05-17 17:14 ` Samuel Thibault [this message]
2023-05-17 18:02 ` Siddhesh Poyarekar
2023-06-06 14:05 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230517171420.iy5zmgai76iagikd@begin \
--to=samuel.thibault@aquilenet.fr \
--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).