From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, michael.d.kinney@intel.com,
Andrew Fish <afish@apple.com>,
Leif Lindholm <quic_llindhol@quicinc.com>
Subject: Re: [edk2-devel] EDK II Coding Standards Specification appears broken
Date: Tue, 3 Jan 2023 09:40:59 -0700 [thread overview]
Message-ID: <2cd04f06-7c97-5a50-910e-21e1a9354196@bsdio.com> (raw)
In-Reply-To: <CO1PR11MB492995BD3F793ED12193BBFDD2F49@CO1PR11MB4929.namprd11.prod.outlook.com>
The top results on Google are for gitbook.io unfortunately.
I've also found the following links that should be updated:
https://github.com/tianocore/tianocore.github.io/wiki/Code-Style-C
The links on this page go to gitbook.com:
https://tianocore-docs.github.io/
This just has the old 2.2 release link:
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Documentation
--
Rebecca Cran
On 1/3/23 08:24, Michael D Kinney wrote:
> Hi Rebecca,
>
> The gitbook.io links are no longer used. All gitbook formatted documents
> are now hosted and published in https://github.com/tianocore-docs
>
> For example, links to latest EDK II C Coding Standards Specification are:
>
> HTML: https://tianocore-docs.github.io/edk2-CCodingStandardsSpecification/draft/
> PDF: https://tianocore-docs.github.io/edk2-CCodingStandardsSpecification/draft/edk2-CCodingStandardsSpecification-draft.pdf
>
> Please let us know what links need to be updated to point at tianocore-docs.
>
> Thanks,
>
> Mike
>
>
>> -----Original Message-----
>> From: Rebecca Cran <rebecca@bsdio.com>
>> Sent: Monday, January 2, 2023 6:14 PM
>> To: edk2-devel-groups-io <devel@edk2.groups.io>; Andrew Fish <afish@apple.com>; Leif Lindholm <quic_llindhol@quicinc.com>; Kinney,
>> Michael D <michael.d.kinney@intel.com>
>> Subject: EDK II Coding Standards Specification appears broken
>>
>> The MAIN branch of the EDK II Coding Standards Specification appears to
>> be broken: all of the pages in
>> https://edk2-docs.gitbook.io/edk-ii-c-coding-standards-specification/
>> are empty.
>>
>> The older release/2.20 version appears to still be working though.
>>
>> --
>> Rebecca Cran
>
>
>
>
>
prev parent reply other threads:[~2023-01-03 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 2:14 EDK II Coding Standards Specification appears broken Rebecca Cran
2023-01-03 15:24 ` Michael D Kinney
2023-01-03 16:40 ` 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=2cd04f06-7c97-5a50-910e-21e1a9354196@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