From: Glen Choo <chooglen@google•com>
To: git@vger•kernel.org, Jacob Keller <jacob.e.keller@intel•com>
Cc: Calvin Wan <calvinwan@google•com>
Subject: Join us for Review Club!
Date: Mon, 27 Mar 2023 15:17:47 -0700 [thread overview]
Message-ID: <kl6lsfdpdek4.fsf@chooglen-macbookpro.roam.corp.google.com> (raw)
Hi all!
Review Club is happening this Wednesday at 14:00 Pacific time (UTC-8).
The goal of the meeting is to help reviewers learn from each other, and
to get better quality feedback up to the list afterwards. We run a
session every other week, and you can find the full schedule on
gitcal [1].
This week, we'll be discussing Jacob Keller's changes to "git blame
--contents" [2]. Let me know if you're interested and would like to join
(off-list is fine), and I'll send you an invite :)
If you're interested but can't make that time, let me know too! E.g.
there has been some interest from folks in Europe, and we'd be glad to
schedule Europe-friendly sessions if that helps more folks join in.
See you there!
[1] http://tinyurl.com/gitcal
[2] https://lore.kernel.org/git/20230324170800.331022-1-jacob.e.keller@intel.com/
next reply other threads:[~2023-03-27 22:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 22:17 Glen Choo [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-17 22:14 Join us for Review Club! 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-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-09-26 22:37 Glen Choo
2022-09-26 22:44 ` Junio C Hamano
2022-09-27 22:01 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=kl6lsfdpdek4.fsf@chooglen-macbookpro.roam.corp.google.com \
--to=chooglen@google$(echo .)com \
--cc=calvinwan@google$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jacob.e.keller@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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