From: rebecca@bsdio.com
To: devel@edk2.groups.io, afish@apple.com
Subject: Re: [edk2-devel] git submodule update --init --recursive
Date: Fri, 23 Aug 2019 16:23:36 -0600 [thread overview]
Message-ID: <35027f0c-51f3-a37a-c94a-b3df084c3981@bsdio.com> (raw)
In-Reply-To: <83E89A1F-25F0-40ED-BE33-6843030DFEE4@apple.com>
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-23 22:23 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 ` rebecca [this message]
2019-08-26 3:54 ` [edk2-devel] " Liming Gao
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=35027f0c-51f3-a37a-c94a-b3df084c3981@bsdio.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