From: Mark Wielaard <mark@klomp.org>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Overseers mailing list <overseers@sourceware.org>,
"CHIGOT, CLEMENT" <clement.chigot@atos.net>
Subject: Re: Write access for GCC not working
Date: Tue, 19 Oct 2021 14:32:24 +0200 [thread overview]
Message-ID: <7da86323d014753e812b4df592a4ec69895fa560.camel@klomp.org> (raw)
In-Reply-To: <CAGWvnym0f6QB1gS+O7J93n7xPfCeVKmZBsnUG8rq21RXSotnOw@mail.gmail.com>
Hi Clément, Hi David,
On Tue, 2021-10-19 at 08:28 -0400, David Edelsohn wrote:
> Please add Clement to the GCC write access.
Done. Please try pushing to the gcc git tree again.
Cheers,
Mark
next prev parent reply other threads:[~2021-10-19 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 11:47 CHIGOT, CLEMENT
2021-10-19 12:27 ` Mark Wielaard
2021-10-19 12:28 ` David Edelsohn
2021-10-19 12:32 ` Mark Wielaard [this message]
2021-10-19 12:34 ` CHIGOT, CLEMENT
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=7da86323d014753e812b4df592a4ec69895fa560.camel@klomp.org \
--to=mark@klomp.org \
--cc=clement.chigot@atos.net \
--cc=dje.gcc@gmail.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).