public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Vineet Gupta <vineet.gupta@linux.dev>
Cc: Overseers mailing list <overseers@sourceware.org>
Subject: Re: Fwd: Fwd: Welcome to sourceware.org
Date: Tue, 29 Nov 2022 22:49:19 +0100	[thread overview]
Message-ID: <Y4Z+X2nrz3jzYzwW@wildebeest.org> (raw)
In-Reply-To: <5032da0a-55bf-1955-2e81-4b086fb224d8@linux.dev>

Hi Vineet,

On Tue, Nov 29, 2022 at 11:55:53AM -0800, Vineet Gupta wrote:
> On 11/29/22 02:19, Mark Wielaard wrote:
> > Note that we now have the private admin-requests@sourceware.org list
> > for these kind of issues.
> 
> Good to know thx. Does this mean overseers is public ?

Yes, it always has been, but we didn't really advertise it.
See https://inbox.sourceware.org/overseers/
https://sourceware.org/mailman/listinfo/overseers

> > You are trying to use your public (.pub) key part.
> 
> Oops I missed that when looking up man page - that did the trick. Thx for
> your quick response.

Happy it works.

And in case you need anything else updated, see also:
https://sourceware.org/sourceware/accountinfo.html

Cheers,

Mark

      reply	other threads:[~2022-11-29 21:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200310183342.35494395A062@sourceware.org>
2022-07-27 20:23 ` Vineet Gupta
2022-07-27 20:35   ` Frank Ch. Eigler
2022-07-27 21:36     ` Vineet Gupta
2022-07-27 21:57       ` Frank Ch. Eigler
2022-07-28  0:38         ` Vineet Gupta
2022-07-28  0:41           ` Frank Ch. Eigler
2022-07-28  0:45             ` Vineet Gupta
     [not found]   ` <05e065ac-eb5c-2c08-1947-0f1c75940031@linux.dev>
2022-11-29 10:19     ` Fwd: " Mark Wielaard
2022-11-29 19:55       ` Vineet Gupta
2022-11-29 21:49         ` Mark Wielaard [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:
  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=Y4Z+X2nrz3jzYzwW@wildebeest.org \
    --to=mark@klomp.org \
    --cc=overseers@sourceware.org \
    --cc=vineet.gupta@linux.dev \
    /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).