From: Steve George <steve@futurile.net>
To: Christina O'Donnell <cdo@mutix.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Coordinators for patch review session on Tuesday
Date: Tue, 2 Apr 2024 21:23:39 +0100 [thread overview]
Message-ID: <t3tujx6bfoa7w5cdkowilb42s5hsvpaeobu4frti6xg6jzbhpo@6vbh62hr62l2> (raw)
In-Reply-To: <b9b31ced-4298-d4c0-fefb-113e7358b890@mutix.org>
On 2 Apr, Christina O'Donnell wrote:
> Hi Steve,
>
> I just wanted to say that I enjoyed the first one of these and I'm looking
> forward to today's session. I did want to go to the last session, but I lost
> track of time and missed it!
>
> I'm a new contributor who's only sent a few patches up, but these sessions
> have been helpful for making contributing feel less intimidating. I haven't
> quite felt comfortable enough to review any patches on my own, so I do like
> the idea of pair-reviewing patches with someone who's a bit more
> experienced.
(...)
Hi Christina - thanks for coming along today - I hope it was useful.
There's good instructions on the Wiki on how to review patches:
https://libreplanet.org/wiki?title=Group:Guix/PatchReviewSessions2024
I would love feedback on how to improve them!
There's plenty of patches to review, I've been keeping a list of them for the patch review calls:
https://debbugs.gnu.org/cgi-bin/pkgreport.cgi?tag=patch-review-hackers-list;users=guix
And the wiki page references some other reports.
Please pick some patches and have a go - if you want someone else to look at them feel free to ping here or on IRC!
Thanks,
Steve / Futurile
next prev parent reply other threads:[~2024-04-02 20:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 21:58 Coordinators for patch review session on Tuesday Steve George
2024-04-02 10:09 ` Christina O'Donnell
2024-04-02 20:23 ` Steve George [this message]
2024-04-03 11:00 ` Christina O'Donnell
2024-04-03 23:01 ` Christina O'Donnell
2024-04-04 14:57 ` Steve George
2024-04-04 17:27 ` Christina O'Donnell
2024-04-05 7:54 ` Steve George
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=t3tujx6bfoa7w5cdkowilb42s5hsvpaeobu4frti6xg6jzbhpo@6vbh62hr62l2 \
--to=steve@futurile.net \
--cc=cdo@mutix.org \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.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).