Bug 30172 - e-mailed patches do not appear in pipermail archive
Summary: e-mailed patches do not appear in pipermail archive
Status: RESOLVED OBSOLETE
Alias: None
Product: sourceware
Classification: Unclassified
Component: Infrastructure (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: overseers mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-25 18:59 UTC by Stas Sergeev
Modified: 2024-02-07 20:56 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed: 2023-02-26 00:00:00


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stas Sergeev 2023-02-25 18:59:48 UTC
I am trying to send patches to libc-alpha@sourceware.org
The patches are being delivered to subscribers
and are available in the public-inbox archive:
https://inbox.sourceware.org/libc-alpha/20230224165400.3417104-1-stsp2@yandex.ru/T/#t

But in the pipermail archive one can only see the cover letters:
https://sourceware.org/pipermail/libc-alpha/2023-February/145872.html
https://sourceware.org/pipermail/libc-alpha/2023-February/145827.html

Some discussion here:
https://sourceware.org/bugzilla/show_bug.cgi?id=30127#c25
Comment 1 Mark Wielaard 2023-02-26 10:32:42 UTC
That is odd, the emails also show up as normal in patchwork:
https://patchwork.sourceware.org/project/glibc/list/?series=17504
https://patchwork.sourceware.org/project/glibc/list/?series=17576
Comment 2 Stas Sergeev 2023-02-26 13:41:25 UTC
Tried this again:
https://sourceware.org/pipermail/libc-alpha/2023-February/145893.html
Now only 1 of 2 patches have passed in.
So the effect is random, but the cover
letter seems to be always passing in,
with the rest - as luck permits.
Comment 3 Mark Wielaard 2024-02-07 20:56:59 UTC
This is really odd. The patches seem to have gone through the mailinglist just fine. And they are in other archives, like inbox and patchwork. It is a mystery why they don't show up in pipermail.

I am sorry to have to close this after a year. Please do reopen or file a new bug if this happens again.