From: Krzysztof Kozlowski <krzk@kernel.org>
To: Linux CH <lch@lists.linux.dev>
Subject: Linux'n'Beer, July 2026
Date: Mon, 29 Jun 2026 14:16:31 +0200 [thread overview]
Message-ID: <49d3a2a8-68bd-4579-8223-bccc0fa61cac@kernel.org> (raw)
Hey everyone,
For next Linux'n'Beer event, I was thinking about Craft Beer Hike,
previously proposed by Christoph.
This is an outdoor event on 11th July around Zurich:
https://craftbeertrail.ch/
It is a hike with visiting local breweries/pubs with good beer. It
requires buying tickets, though.
However, more importantly: not sure if with this weather I could do a
hike/walk in the middle of day. :)
If the weather on 11th July is good, as in not melting, I will probably
go for the hike and we can meet there as well.
But except the hike, let's try to meet in a outside-dining option a bit
earlier:
Date: Thursday, 9th of July 2026, starting at 18:00
Place: Zum Frischen Max, Oerlikon
https://maps.app.goo.gl/spKYFpU1tCtVtKSQ7
Please confirm attendance on 9th of July, by responding to email or on
IRC (Libera/#linuxnbeer-ch) or in Whatsapp group, so I could book
appropriate table.
Best regards,
Krzysztof
next reply other threads:[~2026-06-29 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 12:16 Krzysztof Kozlowski [this message]
2026-06-29 13:12 ` Linux'n'Beer, July 2026 Krzysztof Kozlowski
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=49d3a2a8-68bd-4579-8223-bccc0fa61cac@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