From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: GNU C Library <libc-alpha@sourceware.org>
Subject: [STATS] Auto-update patchwork for committed patches
Date: Tue, 6 Jun 2023 10:05:36 -0400 [thread overview]
Message-ID: <c002198c-4e15-672e-4ecf-7847c068105a@gotplt.org> (raw)
In the last 20 days, there have been 98 commits to glibc and 86 had
matching patches on patchwork. This makes it a success rate of 87.8%.
Here are the commits that were missing from patchwork:
8812b9900e5fba3b696f1b34bd6014211327190f stdlib: Use long long int in
stdlib/tst-llabs: MISSING
9ec31e57278ffc4e680ef03e75ce5b6b02e5edcf hurd: Use __hurd_fail ()
instead of assigning errno: MISSING
9cc27336c9b6fc7b59d1adbf36f0a044a0b89a59 Fix build for
hurd/thread-self.c for i386.: MISSING
0b25c28e028b63c95108c442d8112811107e4c13 Fix misspellings in
sysdeps/powerpc -- BZ 25337: MISSING
ec9a66cd01a73c185bb42cdc032f88b472598feb mach: Fix accessing
mach_i386.h: MISSING
a363f7075125fa654342c69331e6c075518ec28c wchar: Define va_list for POSIX
(BZ #30035): MISSING
a118dc312946ca5347f8f6e8e9221444677bc029 io: Re-flow and sort multiline
Makefile definitions: MISSING
9ffdcf5b79acacffc35506812ca8d99ea1dde618 hurd: Fix setting up signal
thread stack alignment: MISSING
a1950a07583f63f220f30ba7d99ceb619b80ecce riscv: Add the clone3 wrapper:
MISSING
1512599694d0ead4394c0950525fdab09332faf5 io: Re-flow and sort multiline
Makefile definitions: MISSING
7f0d9e61f40c669fca3cfd1e342fa8236c7220b7 Fix all the remaining
misspellings -- BZ 25337: MISSING
d4963a844dc72c4ac14da3395cf511f3d191d689 linux: Fail as unsupported if
personality call is filtered: MISSING
next reply other threads:[~2023-06-06 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 14:05 Siddhesh Poyarekar [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-17 15:30 Siddhesh Poyarekar
2023-05-17 17:14 ` Samuel Thibault
2023-05-17 18:02 ` 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=c002198c-4e15-672e-4ecf-7847c068105a@gotplt.org \
--to=siddhesh@gotplt.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).