public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Wagner <wagi@monom.org>
To: Ralf Mardorf <ralf.mardorf@alice-dsl.net>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [ANNOUNCE] 4.19.245-rt109
Date: Tue, 7 Jun 2022 08:01:06 +0200	[thread overview]
Message-ID: <20220607060106.fee27fea4svhshvv@beryllium.lan> (raw)
In-Reply-To: <20220605144133.604d15a5@archlinux>

Hi Ralf,

On Sun, Jun 05, 2022 at 02:41:48PM +0200, Ralf Mardorf wrote:
> On Sun, 5 Jun 2022 14:18:49 +0200, Ralf Mardorf wrote:
> >Hi Daniel,
> >
> >again it's no joy to import your key ;).
> 
> Pardon, my bad.

No worries. gpg is certainly a tool I will never enjoy.

> 4.19.240-rt108 was seemingly signed by Clark Williams, so I could build
> it without your signature. I forgot to add you to the array of the
> build script before building 4.19.245-rt109.

Correct, Clark took over the release while I was on holiday.

> I'm using different build scripts and you are still not added to all of
> them.
> 
> $ pacman -Q linux-rt{-cornflower,-pussytoes,-securityink,}|cut -d\  -f2
> 4.19.230_rt103-0.300
> 4.19.240_rt108-0.300
> 4.19.237_rt107-0.300
> 4.19.235_rt106-0.1000
> 
> So something on my side went wrong between keyboard and chair ;).

So the first release I did was v4.19.233-rt105. So that means
4.19.230-rt103 should be signed by Clark, the other ones by me.
Clark and I are using the same release scripts which should make the
results more consistent. Not sure where we diverge here.

Thanks,
Daniel

      reply	other threads:[~2022-06-07  6:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27  6:24 [ANNOUNCE] 4.19.245-rt109 Daniel Wagner
2022-05-25  7:31 ` Daniel Wagner
2022-06-05 12:18 ` Ralf Mardorf
2022-06-05 12:41   ` Ralf Mardorf
2022-06-07  6:01     ` Daniel Wagner [this message]

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=20220607060106.fee27fea4svhshvv@beryllium.lan \
    --to=wagi@monom.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=ralf.mardorf@alice-dsl.net \
    /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