From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Michael Halstead <mhalstead@linuxfoundation.org>,
Michael Opdenacker <michael.opdenacker@bootlin.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] docs: add support for mickledore (4.2) release
Date: Thu, 04 May 2023 21:32:10 +0100 [thread overview]
Message-ID: <138930bb46ca53edbad2b186f630bc5688635aab.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADfgfoZ0VtaxPni_Uy1vptxqmmeX9zvvE6C2867v=bt=EnZi9A@mail.gmail.com>
On Thu, 2023-05-04 at 12:47 -0700, Michael Halstead wrote:
> After this patch the docs are labeling both 4.2 and 4.2.999 as
> Mickledore. Is that correct or should 4.2.999 use the
> devbranch name?
4.2.999 is confusing but correct as the code stands today, it means
"latest unreleased mickledore branch". We really need to do something
better.
> Also it marks 4.1.3 as obsolete already. Is that correct or is it
> supported until the end of May?
4.1 is supported until the end of May.
Cheers,
Richard
next prev parent reply other threads:[~2023-05-04 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 22:34 [PATCH] docs: add support for mickledore (4.2) release Michael Halstead
2023-05-04 7:46 ` [docs] " Michael Opdenacker
2023-05-04 19:47 ` Michael Halstead
2023-05-04 20:32 ` Richard Purdie [this message]
2023-05-05 7:31 ` 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=138930bb46ca53edbad2b186f630bc5688635aab.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=docs@lists.yoctoproject.org \
--cc=mhalstead@linuxfoundation.org \
--cc=michael.opdenacker@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox