From: Glen Choo <chooglen@google.com>
To: git@vger.kernel.org
Cc: Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Join us for Review Club!
Date: Tue, 20 Jun 2023 13:42:43 -0700 [thread overview]
Message-ID: <kl6l5y7hsw58.fsf@chooglen-macbookpro.roam.corp.google.com> (raw)
Hi everyone!
Review Club is happening this Wednesday, 21 May, 09:30 Pacific time
(UTC-8). You can find more info at [1] and on gitcal [2]. We run a
session every other week. Note the different time! From the feedback
we've gathered, this time works better for more people, so this will be
the new time for all Review Club sessions going forward. Also, I
apologize for the late announcement this week (Monday was a public
holiday in the USA).
This week, we'll be discussing Phillip Wood's fixes to "git rebase" when
failed picks occur [3]. Let me know if you're interested and would like
to join (off-list is fine), and I'll send you an invite.
See you there!
[1] https://lore.kernel.org/git/Yfl1%2FZN%2FtaYwfGD0@google.com/
[2] http://tinyurl.com/gitcal
[3] https://lore.kernel.org/git/pull.1492.v2.git.1682089074.gitgitgadget@gmail.com/
next reply other threads:[~2023-06-20 20:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 20:42 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-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-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
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=kl6l5y7hsw58.fsf@chooglen-macbookpro.roam.corp.google.com \
--to=chooglen@google.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood@dunelm.org.uk \
/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).