From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/30172] e-mailed patches do not appear in pipermail archive
Date: Sun, 26 Feb 2023 10:32:42 +0000 [thread overview]
Message-ID: <bug-30172-14326-8LoXtUSaRi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30172-14326@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30172
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2023-02-26
Ever confirmed|0 |1
CC| |mark at klomp dot org
Status|UNCONFIRMED |NEW
--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
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
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-02-26 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 18:59 [Bug Infrastructure/30172] New: " stsp at users dot sourceforge.net
2023-02-26 10:32 ` mark at klomp dot org [this message]
2023-02-26 13:41 ` [Bug Infrastructure/30172] " 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-8LoXtUSaRi@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).