public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: overseers@sourceware.org
Subject: Re: [PATCH] fhandler/proc.cc(format_proc_cpuinfo): add Linux 6.1 cpuinfo
Date: Wed, 21 Dec 2022 09:54:42 +0100	[thread overview]
Message-ID: <Y6LJ0qnGMYXMOaM4@calimero.vinschen.de> (raw)
In-Reply-To: <Y6JGN7tZha5D+D4I@wildebeest.org>

On Dec 21 00:33, Mark Wielaard via Overseers wrote:
> Hi Corinna,
> 
> On Tue, Dec 20, 2022 at 09:49:37AM +0100, Corinna Vinschen via Overseers wrote:
> > [Cc overseers, please see especially the end of this mail]
> 
> I haven't had time to look at all issues, but...
> 
> > On Dec 19 15:37, Brian Inglis wrote:
> > > On 2022-12-19 02:13, Corinna Vinschen wrote:
> > > > On Dec 17 14:50, Brian Inglis wrote:
> > > 
> > > I also have a number of emails to Cygwin list owners awaiting moderation by
> > > postmaster-owner@sourceware.org.
> > 
> > I hope overseers can look into that.
> > 
> > I don't understand how your posts could end up at postmaster-owner.
> > They should have ended up at cygwin-patches-owner instead.
> 
> This I can explain. One of the cygwin-patches-owners is
> listadmin@sourceware.org which is really an alias for postmaster,
> which is its own mailman list these days. Which is not very convenient
> since mailman gets confused about the alias, because it doesn't see
> itself (postmaster@) as recipient.
> 
> We should provide something better for listadmin@, but for now I would
> recommend you remove that address under
> https://cygwin.com/mailman/admin/cygwin-patches/?VARHELP=general/owner

Ok, I'll do that.  However, we should have a generic list owner account
which can be used as placeholder and last chance address if the physical
list owners are unavailable for some reason.


Corinna


  reply	other threads:[~2022-12-21  8:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2022-12-20 23:56   ` Mark Wielaard
2022-12-21  8:56     ` Corinna Vinschen
2022-12-21 16:24 Brian Inglis
  -- strict thread matches above, loose matches on Subject: below --
2022-12-20 21:16 Brian Inglis
2022-12-19 22:55 Brian Inglis
2022-12-19 23:25 ` Mark Wielaard

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=Y6LJ0qnGMYXMOaM4@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --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).