From: Anton Mikanovich <amikan@ilbers.de>
To: "Bezdeka, Florian" <florian.bezdeka@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"ibr@ilbers.de" <ibr@ilbers.de>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: Re: [PATCH] changelog: v0.9-rc3
Date: Thu, 23 Jun 2022 21:05:48 +0300 [thread overview]
Message-ID: <70bbe501-3fbb-e27a-baea-11ff4d69fc26@ilbers.de> (raw)
In-Reply-To: <ac6f6a859681c7c778a7cdfed2b3441031f061fc.camel@siemens.com>
22.06.2022 14:54, Bezdeka, Florian wrote:
> Any chance to get this one [1] in as well? Feel free to remove the
> Fixes tag on merge...
>
> [1] https://groups.google.com/g/isar-users/c/F7rxS0C17xg
Looks reasonable, applied.
prev parent reply other threads:[~2022-06-23 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 6:58 Anton Mikanovich
2022-06-22 7:04 ` Anton Mikanovich
2022-06-22 11:54 ` Bezdeka, Florian
2022-06-23 18:05 ` Anton Mikanovich [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=70bbe501-3fbb-e27a-baea-11ff4d69fc26@ilbers.de \
--to=amikan@ilbers.de \
--cc=florian.bezdeka@siemens.com \
--cc=ibr@ilbers.de \
--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