From: Steve George <steve@futurile.net>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: help-guix@gnu.org, guix-devel@gnu.org
Subject: Re: You're invited to the first patch review session!
Date: Fri, 23 Feb 2024 14:59:09 +0000 [thread overview]
Message-ID: <ZdiyvSjBK5E+DpWv@t25sg> (raw)
In-Reply-To: <87sf1kxdhu.fsf@contorta>
Hi Vagrant,
On 22 Feb, Vagrant Cascadian wrote:
> On 2024-02-22, Steve George wrote:
> > We're going to run some online patch review sessions. The first one is on *Thursday, 7th March* and you can sign-up here:
> >
> > https://libreplanet.org/wiki/Group:Guix/PatchReviewSessions2024
>
> Hoping to make it for some of these, thanks for doing it!
>
> One small point is if people could include the scheduled times in UTC in
> addition to "arbitrary" timezones. It is much easier to compare against
> UTC (especially because it does not do daylight savings time) if you
> don't happen to be in one of the specified timezones. :)
(...)
I've put the UTC time into the Wiki page. The Meet-up page should send you a calendar invite which will be correct for your timezone. And, yeah daylight saving and meeting co-ordination is just *hard*! Look forward to seeing you at some of the sessions!
Steve
next prev parent reply other threads:[~2024-02-23 15:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 23:27 You're invited to the first patch review session! Steve George
2024-02-22 23:53 ` Vagrant Cascadian
2024-02-23 6:11 ` Vivien Kraus
2024-02-23 14:59 ` Steve George [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2024-03-01 19:11 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
2024-03-06 11:40 ` Tomas Volf
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZdiyvSjBK5E+DpWv@t25sg \
--to=steve@futurile.net \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=vagrant@debian.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).