From: "Leif Lindholm" <leif.lindholm@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: devel@edk2.groups.io, "Gao, Liming" <liming.gao@intel.com>,
"sssky307@163.com" <sssky307@163.com>,
"'announce@edk2.groups.io'" <announce@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"afish@apple.com" <afish@apple.com>
Subject: Re: [edk2-devel] EDK II Stable Tag release edk2-stable201905 completed
Date: Tue, 11 Jun 2019 17:08:21 +0100 [thread overview]
Message-ID: <20190611160821.t7kqcdoc33nukgut@bivouac.eciton.net> (raw)
In-Reply-To: <6bbebdd6-a90a-ca83-b0af-105afa70a88c@redhat.com>
On Tue, Jun 11, 2019 at 05:46:37PM +0200, Laszlo Ersek wrote:
> > The instructions have spread to many other places (build instructions
> > in wiki and edk2-platforms Readme.md being two of them).
> > That's not to say we shouldn't change it, but that we need to go
> > through and update those places too.
> >
> > And frankly, if we've accepted the need to support submodules, we
> > need to document how edk2 interacts with submodules, not how each
> > individual submodule interacts with edk2 - so the git instructions in
> > OpenSSL-HOWTO.txt should probably be deleted.
> >
> > This might be a good topic to bring to the next design meeting.
> >
> > Presumably the above will be a useful workaround for the original
> > reporter in the meantime.
>
> To be clear -- the problem *exists* only because the original reporter
> is stuck behind a restrictive firewall. There is nothing *technically*
> wrong with the current instructions in "OpenSSL-HOWTO.txt". There is
> nothing particular in how "edk2 interacts with submodules". We're
> discussing workarounds for a political problem.
At this point in time we are discussing a workaround for a political
problem. But relying on submodules means relinquishing elements of
control and consistency (if github goes down, we're consistently
down).
In this instance, we explicitly don't care about the submodule for
that other project (and I really hope this is the norm) - so we
shouldn't be documenting steps that rely on that additional
submodule existing. Whether its inaccessibility is for political (not
just this one, but "oh, someone told me there was pirated things on
that host"), technical ("server went down") or financial ("where is me
domain, me noggin' noggin' domain, it's all gone for beer and
tobacco") reasons.
(Why yes, I may be going slightly loopy from too much python.)
This is why I am referring to anything other than a central definition
of the relationship between edk2 and its submodules as a workaround. I
am not suggesting any shortcomings in the technical aspect.
/
Leif
next prev parent reply other threads:[~2019-06-11 16:08 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 ` [edk2-devel] " krishnaLee
2019-06-10 13:50 ` 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 [this message]
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=20190611160821.t7kqcdoc33nukgut@bivouac.eciton.net \
--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