unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Jack Hill <jackhill@jackhill.us>
Cc: guix-devel@gnu.org
Subject: Re: Help, and get help reviewing patches this Friday (18th)
Date: Thu, 17 Dec 2020 18:19:53 +0000	[thread overview]
Message-ID: <87czz82t2u.fsf@cbaines.net> (raw)
In-Reply-To: <alpine.DEB.2.21.2012171051460.5691@marsh.hcoop.net>

[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]


Jack Hill <jackhill@jackhill.us> writes:

> On Thu, 17 Dec 2020, Christopher Baines wrote:
>
>> Hey,
>>
>> I mentioned in [1] that some "Scheduled and regular collaboration on IRC
>> to review patches" might help both get some patches reviewed, but help
>> get more people involved in reviewing patches, even if they haven't done
>> so before.
>>
>> 1: https://lists.gnu.org/archive/html/guix-devel/2020-11/msg00583.html
>>
>> The suggestion came to do this on a Friday, and I have some time
>> tomorrow (Friday the 18th) that I can set aside to be on IRC and try and
>> help.
>
> Thanks, this sounds like a great initiative, and I'll try to drop
> by. I'm in North America though, so I might be a little tardy (despite
> how much fun the 4am Guix Day was!).

Great, and there's no such thing as being late in this case, well, apart
from me sending the email, it was already tomorrow in some places!

> On the topic of patch review, I was recently asked how I reviewed a
> proposed Go upgrade. I responded on the bug tracker [0]. I'd be
> interested in hearing critiques on the method I used. It might be nice
> to collect some recipes for reviewing different kinds of changes in
> the cookbook :)
>
> [0] https://issues.guix.gnu.org/45161#11

Yeah, this is stuff it would be neat to share. On my side, I've been
working on tooling (Guix Data Service, Guix Build Coordinator) to do a
similar thing (build packages that are affected by patches, and compare
the builds to identify breakages).

Thanks,

Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  reply	other threads:[~2020-12-17 18:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 15:05 Help, and get help reviewing patches this Friday (18th) Christopher Baines
2020-12-17 16:02 ` Jack Hill
2020-12-17 18:19   ` Christopher Baines [this message]
2020-12-18 16:56 ` Ludovic Courtès
2020-12-18 21:09   ` zimoun
2020-12-20 10:25 ` Efraim Flashner

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=87czz82t2u.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=guix-devel@gnu.org \
    --cc=jackhill@jackhill.us \
    /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).