From: Anton Mikanovich <amikan@ilbers.de>
To: "Bezdeka, Florian" <florian.bezdeka@siemens.com>,
"Schmidt, Adriaan" <adriaan.schmidt@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: Re: [PATCH] RECIPE-API-CHANGELOG: Fix typo
Date: Mon, 20 Jun 2022 17:05:19 +0300 [thread overview]
Message-ID: <6268c1fd-ba23-7ead-56cd-c45e3d437800@ilbers.de> (raw)
In-Reply-To: <0a8067bc224cc47d4ca321dbc1c49eb63491efc4.camel@siemens.com>
20.06.2022 17:03, Bezdeka, Florian wrote:
> On Mon, 2022-06-20 at 13:51 +0000, Bezdeka, Florian wrote:
>> That was one of my review commits to the patch series that "introduced"
>> the typo. I'm quite sure that there was a follow up version containing
>> that fix.
>>
>> So my question is: Are you sure that you merged the right version of
>> the patch series? There might be missing more now...
> Something went wrong with v2. See [1]. It claimed to have the fix but
> actually did not. No further steps necessary.
>
> Adriaan, it seems that something went wrong on your end when sending
> out v2.
>
> [1] https://groups.google.com/g/isar-users/c/MGOLSTWd83s/m/ZZHO8zszBgAJ
Yes, the patch `[PATCH v2 1/1] imagetypes: update recipe API changelog`
submitted on the list is exactly what we merged. It didn't include typo fix
(but declared to do so), that's why this typo fix was resend.
That was my fault to do not recheck the text but trust to commit message.
next prev parent reply other threads:[~2022-06-20 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 16:22 Jan Kiszka
2022-06-20 13:41 ` Anton Mikanovich
2022-06-20 13:51 ` Bezdeka, Florian
2022-06-20 14:03 ` Bezdeka, Florian
2022-06-20 14:05 ` Anton Mikanovich [this message]
2022-06-20 14:22 ` Schmidt, Adriaan
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=6268c1fd-ba23-7ead-56cd-c45e3d437800@ilbers.de \
--to=amikan@ilbers.de \
--cc=adriaan.schmidt@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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