public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Michael D Kinney <michael.d.kinney@intel.com>, devel@edk2.groups.io
Cc: Andrew Fish <afish@apple.com>, Leif Lindholm <quic_llindhol@quicinc.com>
Subject: Re: [edk2-devel] [Patch 1/1] Maintainers.txt: Remove Orphan status option
Date: Sun, 5 Nov 2023 11:27:50 +0100	[thread overview]
Message-ID: <8ece1f75-d8ef-62a2-1d4e-527e7d30b5fa@redhat.com> (raw)
In-Reply-To: <20231105011114.812-1-michael.d.kinney@intel.com>

Hi Mike,

On 11/5/23 02:11, Michael D Kinney wrote:
> Cc: Andrew Fish <afish@apple.com>
> Cc: Leif Lindholm <quic_llindhol@quicinc.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
> ---
>  Maintainers.txt | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/Maintainers.txt b/Maintainers.txt
> index 2b03ccbe54aa..cfbde42f2e04 100644
> --- a/Maintainers.txt
> +++ b/Maintainers.txt
> @@ -31,8 +31,6 @@ Descriptions of section entries:
>       Maintained: Someone actually looks after it.
>       Odd Fixes:  It has a maintainer but they don't have time to do
>                   much other than throw the odd patch in. See below.
> -     Orphan:     No current maintainer [but maybe you could take the
> -                 role as you write your new code].
>       Obsolete:   Old code. Something tagged obsolete generally means
>                   it has been replaced by a better system and you
>                   should be using that.

can you perhaps work a few points from your earlier email
<https://edk2.groups.io/g/devel/message/110345> into the commit message?
Something like:

"We would like any proposed change in the edk2 codebase to be assignable
to a human reviewer. If there is a feature for which there is no longer
any support, we should find a way to remove it from the head of the
repository. For critical features, we must find community members that
are willing to own it."

Either way:

Reviewed-by: Laszlo Ersek <lersek@redhat.com>

Thanks
Laszlo



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



      reply	other threads:[~2023-11-05 10:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-05  1:11 [edk2-devel] [Patch 1/1] Maintainers.txt: Remove Orphan status option Michael D Kinney
2023-11-05 10:27 ` Laszlo Ersek [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-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=8ece1f75-d8ef-62a2-1d4e-527e7d30b5fa@redhat.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