public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Fangrui Song via Overseers <overseers@sourceware.org>
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
	Fangrui Song <maskray@google.com>,
	jwakely@redhat.com
Subject: Re: Authenticated access for gcc
Date: Mon, 19 Feb 2024 10:44:55 +0100	[thread overview]
Message-ID: <20240219094455.GJ16832@gnu.wildebeest.org> (raw)
In-Reply-To: <CAFP8O3KgCp3-LX=DB-P2cVzS_-GanABHKxyBCPV=br7Js6+8tg@mail.gmail.com>

Hi Fangrui,

On Sun, Feb 18, 2024 at 11:35:16PM -0800, Fangrui Song via Overseers wrote:
> I think the documentation is up-to-date. I see that the commit
> https://gcc.gnu.org/cgit/gcc-wwwdocs/commit/?id=1e8d94c15d64796ba2ea5abadc3b5e48ff964801
> updated https://gcc.gnu.org/gitwrite.html
> 
> I used overseers@ by mistake as overseers@sourceware.org has been deep
> in my mind... Sorry for the confusion I caused.

No worries. We like to be efficient. But we aren't robots that won't
help you if you use the wrong form to be processed :)

Happy hacking,

Mark

  reply	other threads:[~2024-02-19  9:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14 19:02 Fangrui Song
2024-02-16 10:22 ` Mark Wielaard
2024-02-16 10:51   ` Jonathan Wakely
2024-02-16 12:45     ` Mark Wielaard
2024-02-16 18:46       ` Fangrui Song
2024-02-18 18:10   ` Gerald Pfeifer
2024-02-19  7:35     ` Fangrui Song
2024-02-19  9:44       ` Mark Wielaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-11  3:57 Fangrui Song
2024-01-11 11:34 ` Frank Ch. Eigler
2024-01-11 18:46   ` Fangrui Song

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=20240219094455.GJ16832@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=gerald@pfeifer.com \
    --cc=jwakely@redhat.com \
    --cc=maskray@google.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).