public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Brian.Inglis@shaw.ca, Overseers mailing list <overseers@sourceware.org>
Cc: Corinna Vinschen <corinna@vinschen.de>,
	Brian Inglis <Brian.Inglis@systematicsw.ab.ca>
Subject: Re: [PATCH] fhandler/proc.cc(format_proc_cpuinfo): add Linux 6.1 cpuinfo
Date: Tue, 20 Dec 2022 00:25:21 +0100	[thread overview]
Message-ID: <Y6Dy4QJDv2RxUyv2@wildebeest.org> (raw)
In-Reply-To: <45300667-6612-340b-02a0-600d415e30e0@Shaw.ca>

Hi Brian,

On Mon, Dec 19, 2022 at 03:55:01PM -0700, Brian Inglis via Overseers wrote:
> Hi Corinna,
> 
> And once again I have my fifth moderation message:
> 
> > Subject: Your message to Postmaster awaits moderator approval
> > From: postmaster-owner@sourceware.org
> > To: brian.inglis@shaw.ca
> > Date: Mon, 19 Dec 2022 22:38:06 +0000
> > 
> > Your mail to 'Postmaster' with the subject
> > 
> >     Re: [PATCH] fhandler/proc.cc(format_proc_cpuinfo): add Linux 6.1
> > cpuinfo
> > 
> > Is being held until the list moderator can review it for approval.
> > 
> > The reason it is being held:
> > 
> >     Message has implicit destination

That is really odd. I cannot figure out how your message got to
postmaster. Or what the intended destination was. Would you have the
original message (including full headers) as you sent it?

Thanks,

Mark

  reply	other threads:[~2022-12-19 23:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 22:55 Brian Inglis
2022-12-19 23:25 ` Mark Wielaard [this message]
     [not found] <b2366e8d-f9c3-fc60-bf5d-9131e73360ae@Shaw.ca>
2022-12-20  8:49 ` Corinna Vinschen
2022-12-20 23:33   ` Mark Wielaard
2022-12-21  8:54     ` Corinna Vinschen
2022-12-20 23:56   ` Mark Wielaard
2022-12-21  8:56     ` Corinna Vinschen
2022-12-20 21:16 Brian Inglis
2022-12-21 16:24 Brian Inglis

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=Y6Dy4QJDv2RxUyv2@wildebeest.org \
    --to=mark@klomp.org \
    --cc=Brian.Inglis@shaw.ca \
    --cc=Brian.Inglis@systematicsw.ab.ca \
    --cc=corinna@vinschen.de \
    --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).