public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: rfc@edk2.groups.io, michael.d.kinney@intel.com,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	'Bret Barkelew' <Bret.Barkelew@microsoft.com>
Subject: Re: [edk2-rfc] [RFC] UnitTestFrameworkPkg cmocka submodule alternatives
Date: Thu, 17 Dec 2020 16:54:45 +0100	[thread overview]
Message-ID: <086c08ce-d33e-3ce9-3124-a27db011e5f6@redhat.com> (raw)
In-Reply-To: <e7e23a40-668c-7d0c-6e0d-1559b063e819@redhat.com>

On 12/17/20 15:48, Laszlo Ersek wrote:

> I don't know who or what the <https://github.com/neverware-mirrors>
> organization is, and I'd prefer not fetching code from them automatically.

I'm sorry, this was silly.

The whole point of git is "addressing by content". Our submodule
reference in edk2 makes us check out the cmocka tree at a known hash, so
where that comes from is totally irrelevant.

I'm OK with the proposal as posted.

Thanks & sorry again,
Laszlo


  reply	other threads:[~2020-12-17 15:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 18:45 [RFC] UnitTestFrameworkPkg cmocka submodule alternatives Michael D Kinney
2020-12-17  0:58 ` 回复: [edk2-devel] " gaoliming
2020-12-17 14:48 ` [edk2-rfc] " Laszlo Ersek
2020-12-17 15:54   ` Laszlo Ersek [this message]
2020-12-17 16:01     ` Rebecca Cran
2020-12-17 18:44       ` [EXTERNAL] " Bret Barkelew
2020-12-19 18:58 ` Michael D Kinney
2020-12-19 19:07   ` Bret Barkelew
2020-12-20  1:06   ` [edk2-rfc] " Rebecca Cran
2020-12-21  1:18     ` 回复: [edk2-devel] " gaoliming
2020-12-21 20:14       ` Michael D Kinney
2020-12-21 20:42         ` Rebecca Cran
     [not found]         ` <1652D609A7BB8C97.24251@groups.io>
2020-12-21 20:44           ` Rebecca Cran
2020-12-22  0:41             ` 回复: " gaoliming
2021-02-15  0:43   ` [edk2-devel] " Rebecca Cran
2021-04-06 20:22     ` 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=086c08ce-d33e-3ce9-3124-a27db011e5f6@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