From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Add myself for write after approval
Date: Thu, 30 Jun 2022 23:43:50 -0600 [thread overview]
Message-ID: <a41ee836-eb32-1c8c-d2de-2c823bb9fa0e@gmail.com> (raw)
In-Reply-To: <CAMZc-bw1XHSdGoA8h4-CaGixHFgOjfOAkd9xdfhGZ97dyO2XEw@mail.gmail.com>
On 6/30/2022 8:22 PM, Hongtao Liu via Gcc-patches wrote:
> I think this can be taken as an obvious fix without prior approval.
> "Obvious fixes can be committed without prior approval. Just check in
> the fix and copy it to gcc-patches."
> Quoted from https://gcc.gnu.org/gitwrite.html
If we've given someone write access, they need to be listed in the
MAINTAINERsS file, so yes, this is something I'd consider obvious.
In fact, I thought the template message we sent to folks when they're
given write access includes a request to add a new entry to the
MAINTAINERS file.
Jeff
next prev parent reply other threads:[~2022-07-01 5:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 2:02 Haochen Jiang
2022-07-01 2:22 ` Hongtao Liu
2022-07-01 5:43 ` Jeff Law [this message]
2023-07-31 6:16 Hu, Lin1
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=a41ee836-eb32-1c8c-d2de-2c823bb9fa0e@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.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).