From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, leif.lindholm@linaro.org, "Kinney,
Michael D" <michael.d.kinney@intel.com>
Cc: "Wang, Jian J" <jian.j.wang@intel.com>,
"Gao, Liming" <liming.gao@intel.com>
Subject: [off-topic] Readme.md: add submodule policy and clone commands
Date: Thu, 11 Jul 2019 18:58:54 +0200 [thread overview]
Message-ID: <4c701b2e-5d15-f060-34b3-1de580db34fa@redhat.com> (raw)
In-Reply-To: <20190710171734.m36astajy7v55xur@bivouac.eciton.net>
(off-topic, as marked in the subject)
On 07/10/19 19:17, Leif Lindholm wrote:
> On Wed, Jul 10, 2019 at 05:08:32PM +0000, Kinney, Michael D wrote:
>> Leif,
>>
>> I think the following command has to be run from the git
>> dir that the edk2 repo was cloned into.
>>
>> $ git submodule update --init
>>
>> So I think the correct instructions would be:
>>
>> $ git clone https://github.com/tianocore/edk2.git
>> $ cd edk2
>> $ git submodule update --init
>
> I only said I reviewed it, not that the review was correct ;)
>
> Yeah, good catch. I just mentally filtered out the clone bit.
>
>> $ cd ..
>
> Why would you want to leave?
Heh, that's a good one :) Reminds me of a blog post or similar where the
question was posed (tongue-in-cheek of course), "why boot at all? UEFI
gives you everything!" :)
Thanks!
Laszlo
next prev parent reply other threads:[~2019-07-11 16:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 6:09 [ PATCH v2 0/2] Add edk2 submodule policy Wang, Jian J
2019-07-10 6:09 ` [ PATCH v2 1/2] Readme.md: add submodule policy and clone commands Wang, Jian J
2019-07-10 7:43 ` [edk2-devel] " Liming Gao
2019-07-11 6:32 ` Wang, Jian J
2019-07-10 14:26 ` Leif Lindholm
2019-07-10 17:08 ` Michael D Kinney
2019-07-10 17:17 ` Leif Lindholm
2019-07-10 17:28 ` Michael D Kinney
2019-07-10 17:30 ` Leif Lindholm
2019-07-11 3:32 ` Wang, Jian J
2019-07-11 16:58 ` Laszlo Ersek [this message]
2019-07-10 6:09 ` [ PATCH v2 2/2] CryptoPkg/OpensslLib: remove " Wang, Jian J
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=4c701b2e-5d15-f060-34b3-1de580db34fa@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