From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: "Tummalapalli, Vineela" <vineela.tummalapalli@intel.com>,
YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] ref-manual: move release notes to separate document
Date: Fri, 11 Jun 2021 18:37:36 +0200 [thread overview]
Message-ID: <2b7deb01-bf74-64a1-c068-620660d80034@bootlin.com> (raw)
In-Reply-To: <CAP71WjyrOwdZOKrEO=g52hLjeCP_QKHarGzrAWSuwXYCymDX2A@mail.gmail.com>
Nicolas, Richard,
On 6/11/21 11:52 AM, Nicolas Dechesne wrote:
>
> Side question.. should we move the release notes into the docs
> website? now that it's based on Sphinx, it looks like it would be well
> suited..
Interesting idea, to get a much better looking output. This way we could
have hyperlinks, typically to each commit.
Anyway, that's a generated file, right? What would be the workflow?
Generate the release-notes-<version>.rst file and manually add it to the
yocto-docs directory, even though that's a generated file? What's the
script generating the current release notes, so that I can prepare a
version generating .rst instead?
Cheers,
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-06-11 16:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1675A932C413C877.8243@lists.yoctoproject.org>
2021-06-10 9:35 ` [PATCH] ref-manual: move release notes to separate document Michael Opdenacker
[not found] ` <16872EDF3FBC0621.15202@lists.yoctoproject.org>
2021-06-10 9:39 ` [docs] " Michael Opdenacker
2021-06-10 10:04 ` Nicolas Dechesne
2021-06-10 12:03 ` Michael Opdenacker
[not found] ` <168736F45421387B.20336@lists.yoctoproject.org>
2021-06-11 7:48 ` Michael Opdenacker
2021-06-11 9:15 ` Richard Purdie
2021-06-11 9:52 ` Nicolas Dechesne
2021-06-11 16:37 ` Michael Opdenacker [this message]
2021-06-11 10:13 ` Michael Opdenacker
2021-06-11 17:24 ` Quentin Schulz
2021-06-11 18:04 ` Michael Opdenacker
[not found] ` <16879940C9237AEB.32248@lists.yoctoproject.org>
2021-06-14 8:05 ` Michael Opdenacker
2021-06-14 8:10 ` Quentin Schulz
2021-06-14 13:39 ` Michael Opdenacker
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-all 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=2b7deb01-bf74-64a1-c068-620660d80034@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=nicolas.dechesne@linaro.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=vineela.tummalapalli@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.