From: "Etienne B. Roesch" <etienne.roesch@gmail.com>
To: Andreas Enge <andreas@enge.fr>,
"Etienne B. Roesch" <etienne.roesch@gmail.com>,
Suhail <suhail@bayesians.ca>, Steve George <steve@futurile.net>,
help-guix@gnu.org, guix-devel@gnu.org
Subject: Re: You're invited to the first patch review session!
Date: Wed, 6 Mar 2024 11:36:29 +0000 [thread overview]
Message-ID: <CAPX-MzCXMrpVOuP96xU85FmAfa6hby5P7WeBgVjO9PufhMb4jQ@mail.gmail.com> (raw)
In-Reply-To: <ZehTTVcm16aC4SZZ@ws>
That's the link I have https://meet.jit.si/london-guix-meetup
Etienne
On Wed, Mar 6, 2024 at 11:28 AM Tomas Volf <~@wolfsden.cz> wrote:
> Hi,
>
> On 2024-03-06 10:40:14 +0100, Andreas Enge wrote:
> >
> > Looking forward to tomorrow,
> >
>
> I would just like to point out that the link to the jitsi meeting is not
> on the
> wiki page and was not shared here neither (for those of us who have issues
> with
> meetup.com). I think it was said before the link would be shared
> somewhere, so
> please take this as a reminder (since it is tomorrow already).
>
> Have a nice day,
> Tomas Volf
>
> --
> There are only two hard things in Computer Science:
> cache invalidation, naming things and off-by-one errors.
>
next prev parent reply other threads:[~2024-03-06 11:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 19:11 You're invited to the first patch review session! Suhail
2024-03-05 19:19 ` Etienne B. Roesch
2024-03-06 9:40 ` Andreas Enge
2024-03-06 11:28 ` Tomas Volf
2024-03-06 11:36 ` Etienne B. Roesch [this message]
2024-03-06 11:40 ` Tomas Volf
-- strict thread matches above, loose matches on Subject: below --
2024-02-22 23:27 Steve George
2024-02-22 23:53 ` Vagrant Cascadian
2024-02-23 6:11 ` Vivien Kraus
2024-02-23 14:59 ` Steve George
2024-02-23 19:13 ` Tomas Volf
2024-02-23 20:43 ` indieterminacy
2024-02-29 17:10 ` Daniel Littlewood
2024-02-29 17:35 ` Andreas Enge
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=CAPX-MzCXMrpVOuP96xU85FmAfa6hby5P7WeBgVjO9PufhMb4jQ@mail.gmail.com \
--to=etienne.roesch@gmail.com \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=steve@futurile.net \
--cc=suhail@bayesians.ca \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.