From: Rebecca Cran <rebecca@bluestop.org>
To: "Duran, Leo" <leo.duran@amd.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: vUDK2018: git clone
Date: Sat, 7 Apr 2018 18:12:16 -0600 [thread overview]
Message-ID: <28830f43-65f6-2893-bd34-7385554a14ae@bluestop.org> (raw)
In-Reply-To: <MWHPR12MB18226941C79A38E61B6BCFA0F9B90@MWHPR12MB1822.namprd12.prod.outlook.com>
On 04/07/2018 04:10 PM, Duran, Leo wrote:
> Regarding the "git clone" instructions listed on step "2.iii.a", here:
> https://github.com/tianocore/tianocore.github.io/wiki/UDK2018-How-to-Build
>
> iii. OR Checkout the vUDK2018 Tag from GitHub with the following "git" command
>
> a. run git clone https://github.com/tianocore/edk2.git vUDK2018
>
> Instead of checking out the vUDK2018 Tag, that simply clones the tip of the master branch to a vUDK2018 directory.
>
> So, I'd like to suggest the following changes:
> iii. OR Checkout the vUDK2018 Tag from GitHub with the following "git" command
>
> a. Run: git clone https://github.com/tianocore/edk2.git vUDK2018
>
> b. Go to the vUDK2018 directory, and from there run: git checkout tags/vUDK2018 -b vUDK2018
>
> ... And so on, from there.
It may be better to just add the "-b" parameter, and specify the branch
name instead of the tag - which is UDK2018, instead of vUDK2018. e.g.:
git clone https://github.com/tianocore/edk2.git -b UDK2018
An example on my machine:
bcran@muon:~/workspace % git clone https://github.com/tianocore/edk2.git
-b UDK2018
Cloning into 'edk2'...
remote: Counting objects: 296007, done.
remote: Compressing objects: 100% (106/106), done.
remote: Total 296007 (delta 119), reused 121 (delta 89), pack-reused 295812
Receiving objects: 100% (296007/296007), 268.82 MiB | 10.08 MiB/s, done.
Resolving deltas: 100% (208848/208848), done.
Checking out files: 100% (15552/15552), done.
bcran@muon:~/workspace % cd edk2
bcran@muon:~/workspace/edk2 % git branch
* UDK2018
If you specify the tag, vUDK2018 when cloning, you're put into the
'detached HEAD' state instead.
--
Rebecca
prev parent reply other threads:[~2018-04-08 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-07 22:10 vUDK2018: git clone Duran, Leo
2018-04-08 0:12 ` Rebecca Cran [this message]
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=28830f43-65f6-2893-bd34-7385554a14ae@bluestop.org \
--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