From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"tlaronde@polynum.com" <tlaronde@polynum.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] Documentation errors
Date: Fri, 20 Jan 2023 15:52:13 +0000 [thread overview]
Message-ID: <CO1PR11MB49290DCC030F7079338807E0D2C59@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <Y8qcW/hwFrGVly1a@polynum.com>
Thank you for noticing this issue with the description of the DEC spec on the wiki page.
I have fixed it.
In general, issues with the specs and the wiki page can be entered as BZ, but this
was a simple issue that could be resolved immediately.
Thanks,
Mike
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of tlaronde@polynum.com
> Sent: Friday, January 20, 2023 5:51 AM
> To: devel@edk2.groups.io
> Subject: [edk2-devel] Documentation errors
>
> Context: I continue to explore the EDK II in order to allow NetBSD to
> be a more direct OS host for compilation and testing.
>
> Starting to review the documentation for building (low level: Build), I
> have spotted this:
>
> In:
>
> https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Documentation
>
> in the table describing the EDK II Specifications, the description for
> DEC (Package declaration file) is in fact the description for
> DSC (Description file).
>
> For such things, what is the procedure? Sending notes/patches to the
> list? Entering a BZ?
>
> --
> Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
> http://www.kergis.com/
> http://kertex.kergis.com/
> Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
>
>
>
>
next prev parent reply other threads:[~2023-01-20 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 13:51 Documentation errors tlaronde
2023-01-20 15:52 ` Michael D Kinney [this message]
2023-01-20 16:05 ` [edk2-devel] " tlaronde
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=CO1PR11MB49290DCC030F7079338807E0D2C59@CO1PR11MB4929.namprd11.prod.outlook.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