public inbox for
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <>
Subject: [Bug Infrastructure/30172] e-mailed patches do not appear in pipermail archive
Date: Wed, 07 Feb 2024 20:56:59 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|---                         |OBSOLETE

--- Comment #3 from Mark Wielaard <mark at klomp dot org> ---
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.

You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2024-02-07 20:57 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
2023-02-26 10:32 ` [Bug Infrastructure/30172] " mark at klomp dot org
2023-02-26 13:41 ` stsp at users dot
2024-02-07 20:56 ` mark at klomp dot org [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).