public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Gross <markgross@kernel.org>
To: Mark Gross <markgross@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Danie l Wagner <dwagner@suse.de>,
	Tom Zanussi <tom.zanussi@linux.intel.com>,
	Clark Williams <williams@redhat.com>,
	Junxiao Chang <junxiao.chang@intel.com>
Subject: Re: [ANNOUNCE] 4.9.327-rt197
Date: Thu, 13 Oct 2022 17:29:31 -0700	[thread overview]
Message-ID: <Y0ita2SguCALTawM@T470> (raw)
In-Reply-To: <YzwLK9outbQ/oBhv@ada.ifak-system.com>

On Tue, Oct 04, 2022 at 12:30:03PM +0200, Alexander Dahl wrote:
> Hei Mark,
> 
> Am Fri, Sep 23, 2022 at 01:03:24PM -0700 schrieb Mark Gross:
> > Hello RT-list!
> > 
> > I'm pleased to announce the 4.9.327-rt197 stable release.
> 
> My MUA shows the identical Message-ID for your mail on 4.9.327-rt197
> as for your mail on 4.9.312-rt193 which you send back on Thu, 12 May
> 2022 17:46:22 -0700:
> 
> <165222469651.210737.17409564443317121708@T470>
> 
> How is this even possible? Maybe some issue with some release script?

my workflow normally creates a new "anounce-rt" file and because this time I
was pushing a -next because of merge conflicts I resued my last anounce-rt file
(Message ID and all) and used "mutt -H announce-rt " to send the message.

I should have been more careful.

Sorry for my laziness.

--mark

> 
> I only notice because mutt marked the second one as duplicate.
I also use mutt.

> 
> Greets
> Alex
> 
> > 
> > You can get this release via the git tree at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
> > 
> >   branch: v4.9-rt-next
> >   Head SHA1: d47e3fd2615dbd0aa6eac3745cd209fdd93a868a
> > 
> > 
> > This rebase was a tricky one.  Sebastian provided some patches and I was too
> > dense to figure out where and how to apply them.  My colleague Junxiao did the
> > following and I replicated the steps.
> > 1) convert the v4.9-rt-rebase branch into a quilt series.
> > 2) applied the series to v4.9.327 skipping patches where changes to the random
> > number logic has conflicts.
> > 3) apply the patches Sebastian provided.
> > 4) git quiltimport and pushed it to the above branch.
> > 
> > It seems to compile and it passes the RT BAT testing Junxiao does.
> > 
> > As this was a tricky one I request people to give a good look over.
> > 
> > 
> > Enjoy!
> > Mark Gross
> > 

  reply	other threads:[~2022-10-14  0:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13  0:46 [ANNOUNCE] 4.9.312-rt193 Mark Gross
2022-09-23 20:03 ` [ANNOUNCE] 4.9.327-rt197 Mark Gross
2022-09-23 20:09 ` Mark Gross
2022-09-30 14:58   ` Sebastian Andrzej Siewior
2022-10-14  2:04     ` Mark Gross
2022-10-04 10:30 ` Alexander Dahl
2022-10-14  0:29   ` Mark Gross [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-07  1:46 Mark Gross

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=Y0ita2SguCALTawM@T470 \
    --to=markgross@kernel.org \
    --cc=C.Emde@osadl.org \
    --cc=bigeasy@linutronix.de \
    --cc=dwagner@suse.de \
    --cc=jkacur@redhat.com \
    --cc=junxiao.chang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=tom.zanussi@linux.intel.com \
    --cc=williams@redhat.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