From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"rebecca@bsdio.com" <rebecca@bsdio.com>,
"discuss@edk2.groups.io" <discuss@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] EDK2 doxygen documentation - adding docs for stable tags?
Date: Wed, 10 Nov 2021 02:27:00 +0000 [thread overview]
Message-ID: <CO1PR11MB49290AB9E3FC3B4D7868B21FD2939@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <30cc16f7-0804-7e16-ba78-089b6d338449@bsdio.com>
Hi Rebecca,
Yes. They are useful. I would be better if it could be a CI job on either Azure pipelines
or GitHub Actions could run the tool and publish the documents in TianoCore. Perhaps an on
demand job against a specific tag.
Mike
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Rebecca Cran
> Sent: Tuesday, November 9, 2021 3:20 PM
> To: devel@edk2.groups.io; discuss@edk2.groups.io
> Subject: [edk2-devel] EDK2 doxygen documentation - adding docs for stable tags?
>
> I've been hosting the Doxygen documentation for EDK2 at
> https://bsdio.com/edk2/docs for a few years now. I previously had
> versions for master, UDK2015, UDK2017, UDK2018 etc. but since migrating
> my web server dropped everything except master.
>
>
> I was wondering if people are finding it useful, and if so whether
> they'd like me to generate documentation for each stable tag too?
>
>
> Personally, _I_ find the web-based version (as opposed to a
> locally-generated version) useful for the search feature -- being able
> to quickly find the documentation for a certain function.
>
>
> --
>
> Rebecca Cran
>
>
>
>
>
>
next prev parent reply other threads:[~2021-11-10 2:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 23:19 EDK2 doxygen documentation - adding docs for stable tags? Rebecca Cran
2021-11-10 2:27 ` Michael D Kinney [this message]
2021-11-10 13:40 ` [edk2-discuss] [edk2-devel] " Rebecca Cran
2021-12-01 3:21 ` Michael D Kinney
2021-12-01 16:51 ` Rebecca Cran
2021-12-01 17:02 ` Michael D Kinney
2021-12-05 4:01 ` Michael D Kinney
2021-12-05 4:30 ` Rebecca Cran
2021-12-05 7:09 ` Michael D Kinney
2021-12-08 2:56 ` Rebecca Cran
2021-12-08 2:56 ` Rebecca Cran
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=CO1PR11MB49290AB9E3FC3B4D7868B21FD2939@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