From: Laszlo Ersek <lersek@redhat.com>
To: "Knop, Ryszard" <ryszard.knop@intel.com>, TVKR <tresko1@gmail.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Openssl submodule
Date: Fri, 5 Oct 2018 23:02:39 +0200 [thread overview]
Message-ID: <88f6acf8-96e4-5721-61c1-e3359014e264@redhat.com> (raw)
In-Reply-To: <01F0790E56F0534D8DCAD4AC5838792F6189548B@irsmsx112.ger.corp.intel.com>
On 10/05/18 17:53, Knop, Ryszard wrote:
> Hi,
> Git submodules generally point at a specific commit, so if you go to https://github.com/tianocore/edk2/tree/master/CryptoPkg/Library/OpensslLib and click on the openssl submodule, you'll go to the exact referenced commit (currently d4e4bd2, pointing at the 1.1.0h release). It doesn't point at any specific branch because it's a moving target.
Right.
See the "OpenSSL-Version" section in the file
"CryptoPkg/Library/OpensslLib/OpenSSL-HOWTO.txt". It explains how
CryptoPkg maintainers advance edk2's reference inside OpenSSL's git history.
Thanks
Laszlo
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of TVKR
> Sent: Friday, October 5, 2018 16:55
> To: edk2-devel@lists.01.org
> Subject: [edk2] Openssl submodule
>
> Hi,
>
> It is not clear if the recent change to add OpenSSL as a submodule will pull the code from the master branch of "https://github.com/openssl/openssl"
> or any other branch like "OpenSSL_1_1_0-stable" or "OpenSSL_1_1_1-stable".
> Can some one please clarify?
>
> Thanks
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
> --------------------------------------------------------------------
>
> Intel Technology Poland sp. z o.o.
> ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000 PLN.
>
> Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek
> przegladanie lub rozpowszechnianie jest zabronione.
> This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by
> others is strictly prohibited.
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
>
next prev parent reply other threads:[~2018-10-05 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 14:54 Openssl submodule TVKR
2018-10-05 15:53 ` Knop, Ryszard
2018-10-05 21:02 ` Laszlo Ersek [this message]
2018-10-05 21:03 ` 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=88f6acf8-96e4-5721-61c1-e3359014e264@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