public inbox for
 help / color / mirror / Atom feed
From: "stsp at users dot" <>
Subject: [Bug Infrastructure/30172] e-mailed patches do not appear in pipermail archive
Date: Sun, 26 Feb 2023 13:41:25 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

--- Comment #2 from Stas Sergeev <stsp at users dot> ---
Tried this again:
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.

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

  parent reply	other threads:[~2023-02-26 13:41 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 [this message]
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:

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