public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran via groups.io" <rebecca=os.amperecomputing.com@groups.io>
To: devel@edk2.groups.io, michael.d.kinney@intel.com,
	Rebecca Cran <rebecca@bsdio.com>,
	Leif Lindholm <quic_llindhol@quicinc.com>
Subject: Re: [edk2-devel] [PATCH edk2-platforms 1/1] Prepare for move to GitHub Pull Request workflow
Date: Fri, 26 Jul 2024 11:42:08 -0600	[thread overview]
Message-ID: <313474e0-f52a-4090-9ac8-c289af3e6716@os.amperecomputing.com> (raw)
In-Reply-To: <CO1PR11MB4929D4B256C8E4982612E1CDD2B42@CO1PR11MB4929.namprd11.prod.outlook.com>

On 7/26/24 11:37, Michael D Kinney via groups.io wrote:

> Members with more than one email address is confusing.  Can we
> limit to single email address for TianoCore activities?
> 
> Also, should Maintainer.txt be removed yet?  There is a GitHub
> Action active in edk2 now that assigns reviews from Maintainer.txt.

Sure, I can have all my edk2-platforms work under my 
os.amperecomputing.com email.

I'd like to remove Maintainers.txt now to avoid _another_ file that can 
get out of sync. I know edk2 has chosen to use the Github Action for 
now, but I'd prefer edk2-platforms to move directly to using CODEOWNERS 
(and in a few days, REVIEWERS when I write the script to handle it).

-- 
Rebecca


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120051): https://edk2.groups.io/g/devel/message/120051
Mute This Topic: https://groups.io/mt/107560952/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-07-26 17:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-26 13:20 [edk2-devel] [PATCH edk2-platforms 1/1] Prepare for move to GitHub Pull Request workflow Rebecca Cran
2024-07-26 13:29 ` Rebecca Cran
2024-07-26 17:37   ` Michael D Kinney
2024-07-26 17:42     ` Rebecca Cran via groups.io [this message]
2024-07-26 18:11       ` Michael D Kinney

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-list 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=313474e0-f52a-4090-9ac8-c289af3e6716@os.amperecomputing.com \
    --to=devel@edk2.groups.io \
    /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