stable-rt.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	stable-rt@vger.kernel.org
Subject: Re: Stable backports
Date: Wed, 28 Jun 2023 10:28:23 -0400	[thread overview]
Message-ID: <d743d4bf-cade-5fd6-1745-cb3d5742e929@canonical.com> (raw)
In-Reply-To: <20230628040801.67d42348@rorschach.local.home>



On 6/28/23 04:08, Steven Rostedt wrote:
> On Tue, 27 Jun 2023 15:14:35 -0400
> Joseph Salisbury <joseph.salisbury@canonical.com> wrote:
>
>> The latest two commits are still in linux-next and have not landed in
>> mainline as of yet (d15121be7485 and 2951580ba6ad).  Should I wait to
>> add them to the v5.15-rt stable tree and see if Greg adds them to his
>> trees first?
> Well, they are in mainline now ;-)
>
> But I just want to point out that our "upstream" is the next RT kernel
> that we have. That is, you should wait till 6.1-rt has a commit before
> you take it. 6.1 should wait till Sebastian's 6.3-rt has it.
>
> That is, if a commit goes into Sebastion's tree, it's OK to backport.
> But those backports are always added separately from merging a mainline
> stable branch.
>
> We merge stable branches by themselves and increment the -rt number
> (and we do not need to post a shortlog for that, even though srt does).
>
> Then we add backports as a separate release (and increment the -rt
> number again).
>
> -- Steve
>

This all makes sense to me now.  Thanks so much for the feedback, 
Sebastian and Steven!



  reply	other threads:[~2023-06-28 14:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-20 15:03 Stable backports Sebastian Andrzej Siewior
2023-06-27 19:14 ` Joseph Salisbury
2023-06-28  6:56   ` Sebastian Andrzej Siewior
2023-06-28  8:08   ` Steven Rostedt
2023-06-28 14:28     ` Joseph Salisbury [this message]
2023-07-27 10:50 ` Sebastian Andrzej Siewior

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=d743d4bf-cade-5fd6-1745-cb3d5742e929@canonical.com \
    --to=joseph.salisbury@canonical.com \
    --cc=bigeasy@linutronix.de \
    --cc=rostedt@goodmis.org \
    --cc=stable-rt@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).