From: "Liming Gao" <liming.gao@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"rebecca@bsdio.com" <rebecca@bsdio.com>,
"afish@apple.com" <afish@apple.com>
Subject: Re: [edk2-devel] git submodule update --init --recursive
Date: Mon, 26 Aug 2019 03:54:01 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E4DC1E6@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <35027f0c-51f3-a37a-c94a-b3df084c3981@bsdio.com>
edk2\Readme.md Submodules section gives the command to update edk2 project.
Thanks
Liming
>-----Original Message-----
>From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
>rebecca@bsdio.com
>Sent: Saturday, August 24, 2019 6:24 AM
>To: devel@edk2.groups.io; afish@apple.com
>Subject: Re: [edk2-devel] git submodule update --init --recursive
>
>On 2019-08-23 14:41, Andrew Fish via Groups.Io wrote:
>> I was following the instructions on how to build OVMF and my build failed. It
>looks like the reason it failed was because I did not do a `git submodule
>update --init --recursive`. It would be good if we could make how to clone the
>edk2 instructions a bit more obvious.
>
>
>I think we came to the conclusion that "--recursive" isn't needed. But
>I've found that there are cases where "--force" is required to make sure
>git checks out a submodule correctly.
>
>
>--
>Rebecca Cran
>
>
>
next prev parent reply other threads:[~2019-08-26 3:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 20:41 git submodule update --init --recursive Andrew Fish
2019-08-23 22:23 ` [edk2-devel] " rebecca
2019-08-26 3:54 ` Liming Gao [this message]
2019-08-26 21:59 ` Andrew Fish
2019-08-26 22:11 ` Michael D Kinney
2019-08-26 22:29 ` Andrew Fish
2019-08-27 13:37 ` Laszlo Ersek
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=4A89E2EF3DFEDB4C8BFDE51014F606A14E4DC1E6@SHSMSX104.ccr.corp.intel.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