From: Nicolas Graves via <help-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Nicolas Graves via" <help-guix@gnu.org>
Subject: Re: managing waiting patches
Date: Wed, 10 Aug 2022 00:02:04 +0200 [thread overview]
Message-ID: <874jylgjoj.fsf@ngraves.fr> (raw)
In-Reply-To: <87tu6l2l54.fsf@gnu.org>
On 2022-08-09 22:54, Ludovic Courtès wrote:
> This was discussed recently on guix-devel and I hope we can collectively
> improve on that. The new teams that we devised (see ‘etc/teams.scm’)
> should help, though we have yet to document them and publicize them.
Thanks for your answer, I'll check that.
> I don’t have any great suggestion here—you already seem to be doing
> things rationally. In general, short, to-the-point patch series are
> more likely to be reviewed quickly, so that’s one strategy you can adopt
> here. And then you can locally keep branches for each part of the
> broader patch series, possibly rebasing them until they’re applied.
I finally went for the branching strategy, hence my patch frenzy trying
to sort everything I wrote in well-ordered branches in one repo. Takes
some time but I'll close to that.
> You could send an updated patch series with the new version as v2; that
> would also serve as a reminder for reviewers.
>
> Using ./etc/teams.scm you can also look for people working in this area
> that you could ping.
>
> Last, if you’re on IRC, you’re welcome to occasionally ping people
> there.
Thanks for the advice. Not an IRC user for now, maybe I will come
someday.
Is there a requirement to help with patch reviewing? I feel I can tackle
python or rust packages unless they are weird, I need not to spend too
much time on that, but if it's just advising new beginners (I'm myself
a 9 month old Guix user but went cold turkey on my main machine, while
my first patches were a nightmare, now I hope/believe they are quite
clean) or trying to patch and build locally for <1h a day, with
proper guidelines I might be able to help here.
--
Best regards,
Nicolas Graves
next prev parent reply other threads:[~2022-08-09 22:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 22:59 managing waiting patches Nicolas Graves via
2022-08-09 20:54 ` Ludovic Courtès
2022-08-09 22:02 ` Nicolas Graves via [this message]
2022-09-05 19:45 ` Ludovic Courtès
2022-09-09 17:08 ` zimoun
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=874jylgjoj.fsf@ngraves.fr \
--to=help-guix@gnu.org \
--cc=ludo@gnu.org \
--cc=ngraves@ngraves.fr \
/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.
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).