From: Glen Choo <chooglen@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org,
Christophe Poucet <christophe.poucet@gmail.com>,
Josh Steadmon <steadmon@google.com>
Subject: Re: Join us for Review Club!
Date: Tue, 27 Sep 2022 15:01:54 -0700 [thread overview]
Message-ID: <kl6lbkr0mq7h.fsf@chooglen-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <xmqqr0zxah7x.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
> Glen Choo <chooglen@google.com> writes:
>
>> [2] http://tinyurl.com/gitcal
>> Note that the gitcal event is a little out of date; it should say
>> say "Please contact Josh Steadmon <steadmon@google.com> _and_ Glen
>> Choo <chooglen@google.com>...".
>
> I can make that happen, but do you really want both of them to be
> contacted?
Yes, I'd prefer that both of us get the email in case either us is
unavailable. In the longer term, if Review Club is more of a
project-wide effort instead of Google-specific (which I really hope will
happen :)), we'll find a better approach than "email all admins".
> Also do you (or Josh) want a write access to update
> these details? You two clearly have a demonostrated need to such an
> access.
Yes, giving both of us write access sounds very helpful, thanks!.
next prev parent reply other threads:[~2022-09-27 22:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 22:37 Join us for Review Club! Glen Choo
2022-09-26 22:44 ` Junio C Hamano
2022-09-27 22:01 ` Glen Choo [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-17 22:14 Glen Choo
2023-07-18 4:40 ` Luna Jernberg
2023-07-18 16:40 ` Glen Choo
2023-07-18 17:03 ` Glen Choo
2023-06-20 20:42 Glen Choo
2023-06-06 19:56 Calvin Wan
2023-03-27 22:17 Glen Choo
2023-03-13 23:23 Calvin Wan
2023-03-15 17:54 ` Derrick Stolee
2023-02-27 22:03 Glen Choo
2023-02-14 20:44 Calvin Wan
2023-02-14 22:39 ` M Hickford
2023-01-31 19:41 Calvin Wan
2022-12-05 21:33 Glen Choo
2022-11-22 0:02 Glen Choo
2022-11-07 23:15 Glen Choo
2022-10-25 17:10 Glen Choo
2022-02-01 18:03 Josh Steadmon
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=kl6lbkr0mq7h.fsf@chooglen-macbookpro.roam.corp.google.com \
--to=chooglen@google.com \
--cc=christophe.poucet@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=steadmon@google.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 public inbox
https://80x24.org/mirrors/git.git
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).