From: Krzysztof Kozlowski <krzk@kernel.org>
To: Linux CH <lch@lists.linux.dev>
Subject: Re: Linux'n'Beer, July 2026
Date: Thu, 16 Jul 2026 13:05:59 +0200 [thread overview]
Message-ID: <27af0ed4-2fa0-4f3d-955a-94858f0a19bc@kernel.org> (raw)
In-Reply-To: <6fd9c592-bf53-4f54-9036-57cf821723d4@kernel.org>
On 13/07/2026 22:31, Krzysztof Kozlowski wrote:
> On 29/06/2026 15:12, Krzysztof Kozlowski wrote:
>> On 29/06/2026 14:16, Krzysztof Kozlowski wrote:
>>
>> Change of plans! Embedded software meetup happens that time, so let's
>> not create conflicting events.
>>
>> New planned time, one week later - 16th July:
>>
>> Date: Thursday, 16th of July 2026, starting at 18:00
>> Place: Zum Frischen Max, Oerlikon
>> https://maps.app.goo.gl/spKYFpU1tCtVtKSQ7
>
>
> Just a reminder folks, this Thursday, 16th of July, next beer meetup at
> Zum Frischen Max, Oerlikon.
I did not book a table, for sure we will find something. I'll have
Linux'n'beer logo to be easier to find.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-07-16 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 12:16 Linux'n'Beer, July 2026 Krzysztof Kozlowski
2026-06-29 13:12 ` Krzysztof Kozlowski
2026-07-13 20:31 ` Krzysztof Kozlowski
2026-07-16 11:05 ` Krzysztof Kozlowski [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=27af0ed4-2fa0-4f3d-955a-94858f0a19bc@kernel.org \
--to=krzk@kernel.org \
--cc=lch@lists.linux.dev \
/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