public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "krishnaLee" <sssky307@163.com>
To: devel@edk2.groups.io
Cc: "'announce@edk2.groups.io'" <announce@edk2.groups.io>,
	 "leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
	 "Kinney, Michael D" <michael.d.kinney@intel.com>,
	 "afish@apple.com" <afish@apple.com>,
	 "Laszlo Ersek (lersek@redhat.com)" <lersek@redhat.com>
Subject: Re: [edk2-devel] EDK II Stable Tag release edk2-stable201905 completed
Date: Mon, 10 Jun 2019 17:06:44 +0800 (CST)	[thread overview]
Message-ID: <7606aa6e.d162.16b40a3cb45.Coremail.sssky307@163.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E46CD3D@SHSMSX104.ccr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1514 bytes --]

Hi,
I had download it (git clone -b edk2-stable201905 https://github.com/tianocore/edk2.git),
but update openssl failed by command (git submodule update --init --recursive)
Cloning into 'D:/edk2/CryptoPkg/Library/OpensslLib/openssl/boringssl'...
fatal: unable to access 'https://boringssl.googlesource.com/boringssl/': Failed to connect to boringssl.googlesource.com port 443: Timed out


I think many chinese people need "Climbing over the Wall" to access 'https://boringssl.googlesource.com/boringssl/'.


I am sorry about this but is there any other idea to bypass it?




thanks,
Krishna.






At 2019-06-06 17:54:48, "Liming Gao" <liming.gao@intel.com> wrote:


Hi, all

 

The tag edk2-stable201905 has been created. https://github.com/tianocore/edk2/releases/tag/edk2-stable201905

  git clone -b edk2-stable201905 https://github.com/tianocore/edk2.git

 

The tag edk2-stable201905 has been added into the main EDK II Wiki page.

  https://github.com/tianocore/tianocore.github.io/wiki/EDK-II

 

The quiet period has now ended. Thank you for your cooperation and patience. Normal commits can now be resumed.

 

Next edk2 stable tag (edk2-stable201908) planning has been added into wiki page.

https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning.

 

If you have ideas for features in the next stable tag, please enter a Bugzilla for evaluation. Please let us know if there are existing open Bugzilla entries that should be targeted at this next stable tag.

 

Thanks

Liming


[-- Attachment #2: Type: text/html, Size: 5687 bytes --]

  reply	other threads:[~2019-06-10  9:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06  9:54 EDK II Stable Tag release edk2-stable201905 completed Liming Gao
2019-06-10  9:06 ` krishnaLee [this message]
2019-06-10 13:50   ` [edk2-devel] " Liming Gao
2019-06-10 14:00     ` Leif Lindholm
2019-06-10 14:16       ` Liming Gao
2019-06-12  5:24         ` krishnaLee
2019-06-11 10:08       ` Laszlo Ersek
2019-06-11 10:30         ` Leif Lindholm
2019-06-11 15:46           ` Laszlo Ersek
2019-06-11 16:08             ` Leif Lindholm
2019-06-12  8:18               ` Laszlo Ersek
2019-06-12  9:21                 ` Leif Lindholm
2019-06-12  9:37                   ` Laszlo Ersek
2019-06-12 13:30                     ` Liming Gao
2019-06-12 17:00                       ` Leif Lindholm

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=7606aa6e.d162.16b40a3cb45.Coremail.sssky307@163.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