public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Jayaprakash, N" <n.jayaprakash@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"rebecca@bsdio.com" <rebecca@bsdio.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] Migrating edk2-libc to use GitHub PR review process
Date: Wed, 7 Aug 2024 09:10:37 +0000	[thread overview]
Message-ID: <PH7PR11MB5943379BF9A75678D784564FEEB82@PH7PR11MB5943.namprd11.prod.outlook.com> (raw)
In-Reply-To: <f49ff60e-46f1-4973-b069-97c25609688a@bsdio.com>

Thanks Rebecca.

I am going through this and get back to you for any help soon.

Regards,
JP

-----Original Message-----
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Rebecca Cran
Sent: Tuesday, August 6, 2024 4:16 PM
To: Jayaprakash, N <n.jayaprakash@intel.com>; devel@edk2.groups.io
Cc: Kinney, Michael D <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] Migrating edk2-libc to use GitHub PR review process

On 8/6/2024 3:10 AM, Jayaprakash, N wrote:
>
> Hi Rebecca,
>
> Mike suggested me to talk to you to see the possibility of getting 
> edk2-libc repo to the GitHub PR review process.
>
> It’s a relatively small repo with few contributors.
>
> Would like to understand what it takes to migrate to the new process? 
> Would you be able to help in this migration?
>
I'd be happy to help! We just need to move Maintainers.txt to CODEOWNERS and create a CONTRIBUTORS.md file (there aren't any reviewers, so we don't need a REVIEWERS file) and we can start using pull requests.


See the patch I sent out for edk2-platforms for an example: 
https://edk2.groups.io/g/devel/message/120195


--
Rebecca








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



  reply	other threads:[~2024-08-07  9:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06  9:10 [edk2-devel] Migrating edk2-libc to use GitHub PR review process Jayaprakash, N
2024-08-06 10:46 ` Rebecca Cran
2024-08-07  9:10   ` Jayaprakash, N [this message]
     [not found]   ` <17E9673DCCBF2128.19172@groups.io>
2024-09-04 15:24     ` Jayaprakash, N

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=PH7PR11MB5943379BF9A75678D784564FEEB82@PH7PR11MB5943.namprd11.prod.outlook.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