All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Quentin Schulz" <quentin.schulz@streamunlimited.com>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Nicolas Dechesne <nicolas.dechesne@linaro.org>,
	"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: Mon, 14 Jun 2021 10:10:21 +0200	[thread overview]
Message-ID: <20210614081021.zoh3ph7mgtjuui5u@qschulz> (raw)
In-Reply-To: <4f3eab88-a3c2-f386-1cdb-f775785afe5f@bootlin.com>

Hi Michael,

On Mon, Jun 14, 2021 at 10:05:31AM +0200, Michael Opdenacker wrote:
> Hi Quentin,
> 
> On 6/11/21 8:04 PM, Michael Opdenacker wrote:
> > HI Quentin,
> >
> > On 6/11/21 7:24 PM, Quentin Schulz wrote:
> >> I can't. I only have a fileserver webpage on which I can click on ../
> >> which redirects me to http://docs.yoctoproject.org/
> > Oops, maybe because my "master-next" branch was broken until 15 minutes
> > ago. This is fixed now but the autobuilder may need time to update the
> > contents.
> >
> > Thanks for the notification.
> 
> 
> That's fixed now if you're interested in having a look:
> https://docs.yoctoproject.org/next/

I was about to say that it finally works now, it didn't over the
week-end.

Thanks for the update!

I was wondering if it made more sense to pick more expressive words for
"current" and "previous" release manuals. Something like
maintained/unmaintained for example? Or... EOL/outdated for the second
kind?

Also, I would move the release number after the release name, because
it's the place where you usually have section number in e.g. Reference
Manual in the navigation panel.

In any case, looks already great to me!
Thanks Michael!
Cheers,
Quentin

  reply	other threads:[~2021-06-14  8:10 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
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 [this message]
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=20210614081021.zoh3ph7mgtjuui5u@qschulz \
    --to=quentin.schulz@streamunlimited.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=michael.opdenacker@bootlin.com \
    --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.