From: Steve George <steve@futurile.net>
To: jgart <jgart@dismail.de>, Arun Isaac <arunisaac@systemreboot.net>,
Christopher Baines <mail@cbaines.net>,
Andreas Enge <andreas@enge.fr>,
Simon Tournier <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Committers available for Patch hacking/review meet-up?
Date: Thu, 15 Feb 2024 08:36:49 +0000 [thread overview]
Message-ID: <4258aa2f-60ee-44d5-a585-9aa6d9f12e2c@futurile.net> (raw)
In-Reply-To: <a8ddba7eff3bec08937d34e7a06ddeffcaf60750@dismail.de>
On 15/02/2024 00:53, jgart wrote:
>> 7th March (Thursday)
>> 20th March (Wednesday)
>> 2nd April (Tuesday)
>> 15th April (Monday)
>> 3rd May (Friday)
>> 16th May (Thursday)
>> 29th May (Wednesday)
>>
>> Each one held at 19:00 CET / 18:00 BST / 13:00 EST [0] for 1.5 hours.
>
> Hi,
>
> Thanks for putting this together.
>
> Lately I've been too busy with work and other tasks/priorities to review Guix patches, unfortunately.
>
> Those dates and times conflict with my work hours so I probably won't be able to attend any of the proposed dates.
>
> I live in the CT timezone and I am usually working from 9 AM to 5 or 6 PM CT on weekdays.
>
> I could potentially do a Saturday or Sunday sometime in May.
>
> all best,
>
> jgart
>
> https://whereis.みんな/
Hi Jgart - understood and no worries - sorry about the timing, hard to
find something that works for everyone. If you don't mind I'll email you
a bit closer to May and see what your calendar is like - then we can see
if organising something on a weekend or maybe recording a video would be
possible.
Thanks,
Steve
prev parent reply other threads:[~2024-02-15 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 14:48 Committers available for Patch hacking/review meet-up? Steve George
2024-02-14 14:04 ` Andreas Enge
2024-02-15 8:34 ` Steve George
2024-02-14 14:20 ` Simon Tournier
2024-02-15 0:53 ` jgart
2024-02-15 8:36 ` Steve George [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=4258aa2f-60ee-44d5-a585-9aa6d9f12e2c@futurile.net \
--to=steve@futurile.net \
--cc=andreas@enge.fr \
--cc=arunisaac@systemreboot.net \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
--cc=mail@cbaines.net \
--cc=zimon.toutoune@gmail.com \
/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.