From: Florian Weimer <fweimer@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: libc-alpha@sourceware.org
Subject: Re: Monday patch review meeting: Storm brewing in Pune
Date: Mon, 12 Apr 2021 13:23:36 +0200 [thread overview]
Message-ID: <87sg3vlpaf.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <73560644-5bc8-b432-cd88-e7e675cc9444@gotplt.org> (Siddhesh Poyarekar's message of "Mon, 12 Apr 2021 16:48:10 +0530")
* Siddhesh Poyarekar:
> I was supposed to start today's call bridge since Carlos is away, but
> things don't look good out here. There's a pretty bad storm brewing
> and the internet has already gone out once. If the bridge doesn't
> start then it means that my network is gone, so please continue the
> review on IRC or something.
>
> Alternatively, is anybody else here an FSF associate member and can
> start the call?
If people are fine with using Bluejeans, we could use that. It works
very well in web browsers, but of course uses proprietary Javascript.
Thanks,
Florian
prev parent reply other threads:[~2021-04-12 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 11:18 Siddhesh Poyarekar
2021-04-12 11:23 ` Florian Weimer [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=87sg3vlpaf.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).