From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: Isar 0.9
Date: Tue, 28 Jun 2022 14:21:28 +0200 [thread overview]
Message-ID: <YrrySKTovKqDuxLU@ilbers.de> (raw)
In-Reply-To: <20220628122243.2e7dec72@md1za8fc.ad001.siemens.net>
On Tue, Jun 28, 2022 at 12:22:43PM +0200, Henning Schild wrote:
> Good effort! I am personally always trying to follow next, but nice to
> see another release.
Thanks Henning for the positive feedback, I do appreciate it :) . We didn't tag
often due to the manual testing involved; we'll look at automating the testing
on real hardware.
With kind regards,
Baurzhan
prev parent reply other threads:[~2022-06-28 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 9:18 Anton Mikanovich
2022-06-28 10:22 ` Henning Schild
2022-06-28 12:21 ` Baurzhan Ismagulov [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=YrrySKTovKqDuxLU@ilbers.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.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