public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "Czajkowski, Maciej" <maciej.czajkowski@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] Request for access for edk2-staging branch creation
Date: Mon, 6 Nov 2023 21:51:51 +0000	[thread overview]
Message-ID: <CO1PR11MB4929B386F5FBA2BC96AAAA29D2AAA@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <IA1PR11MB7728D4A0C83C00AF2C493C04F8D4A@IA1PR11MB7728.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1623 bytes --]

Hi,

Can you please follow up with your Github ID and the additional details in a patch email wit Readme.MD content?

https://github.com/tianocore/edk2-staging/blob/about/README

4) Process to add a new feature to edk2-staging
                a) Maintainer sends patch email to edk2-devel mailing list announcing the creation of a new
        feature branch in edk2-staging with Readme.MD.  Readme.MD is in root of feature branch
        with summary, owners, timeline, links to related materials.
                b) Maintainer creates feature branch in edk2-staging
                c) Maintainer is responsible for making sure feature is frequently synced to edk2/master

Thanks,

Mike


From: Czajkowski, Maciej <maciej.czajkowski@intel.com>
Sent: Thursday, October 19, 2023 6:48 AM
To: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>
Subject: [edk2-devel] Request for access for edk2-staging branch creation

Hello,

I would like to request for a write access to edk2-staging repository to create a new branch for DeviceSimPkg. Its goal is to provide an environment to write OS-executable tests for code that interacts directly with devices.

Regards,
Maciej Czajkowski


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



[-- Attachment #2: Type: text/html, Size: 5493 bytes --]

      reply	other threads:[~2023-11-06 21:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19 13:47 [edk2-devel] Request for access for edk2-staging branch creation Maciej Czajkowski
2023-11-06 21:51 ` Michael D Kinney [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=CO1PR11MB4929B386F5FBA2BC96AAAA29D2AAA@CO1PR11MB4929.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