public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Nate DeSimone <nathaniel.l.desimone@intel.com>, devel@edk2.groups.io
Cc: Andrew Fish <afish@apple.com>,
	Leif Lindholm <leif.lindholm@linaro.org>,
	Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [PATCH 0/2] EdkRepo - The Multi-Repository Tool for EDK II
Date: Wed, 12 Jun 2019 09:54:26 +0200	[thread overview]
Message-ID: <b928a32e-8b95-2fef-18ba-407a6b877590@redhat.com> (raw)
In-Reply-To: <20190612000448.20432-1-nathaniel.l.desimone@intel.com>

Hi Nate,

On 06/12/19 02:04, Nate DeSimone wrote:
> This patch series is raised to add the EdkRepo and EdkRepo-Manifest branches
> to the Edk2-Staging repository. These branches are added to host EdkRepo,
> the multi-repository tool for EDK II firmware development to TianoCore.
> 
> For more details on EdkRepo, please see my RFC.
> 
> Nate DeSimone (2):
>   Add EdkRepo - The Multi-Repo Tool
>   Add EdkRepo manifest XML
> 

the Maintainers.txt files added in both patches contain sections called
"EDK II" and "EDK II Packages". Is that intended? (I'm not familiar with
branches in the staging repo.)

No comments from me otherwise, I'll defer to the other stewards on this.

Thanks!
Laszlo

  parent reply	other threads:[~2019-06-12  7:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12  0:04 [PATCH 0/2] EdkRepo - The Multi-Repository Tool for EDK II Nate DeSimone
2019-06-12  0:04 ` [PATCH 1/2] [staging/EdkRepo]: Add EdkRepo - The Multi-Repo Tool Nate DeSimone
2019-06-12  0:04 ` [PATCH 2/2] [staging/EdkRepo-Manifest]: Add EdkRepo manifest XML Nate DeSimone
2019-06-12  7:54 ` Laszlo Ersek [this message]
2019-06-12 15:41   ` [edk2-devel] [PATCH 0/2] EdkRepo - The Multi-Repository Tool for EDK II Nate DeSimone
2019-06-14 21:39 ` 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=b928a32e-8b95-2fef-18ba-407a6b877590@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