From: "stsp at users dot sourceforge.net" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/30172] New: e-mailed patches do not appear in pipermail archive
Date: Sat, 25 Feb 2023 18:59:48 +0000 [thread overview]
Message-ID: <bug-30172-14326@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30172
Bug ID: 30172
Summary: e-mailed patches do not appear in pipermail archive
Product: sourceware
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: Infrastructure
Assignee: overseers at sourceware dot org
Reporter: stsp at users dot sourceforge.net
Target Milestone: ---
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
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-02-25 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 18:59 stsp at users dot sourceforge.net [this message]
2023-02-26 10:32 ` [Bug Infrastructure/30172] " mark at klomp dot org
2023-02-26 13:41 ` stsp at users dot sourceforge.net
2024-02-07 20:56 ` mark at klomp dot org
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=bug-30172-14326@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=overseers@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).