From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 59513@debbugs.gnu.org, Christopher Baines <mail@cbaines.net>,
Liliana Marie Prikler <liliana.prikler@gmail.com>,
zimoun <zimon.toutoune@gmail.com>
Subject: [bug#59513] [PATCH v2] doc: contributing: Tweak the Commit Policy.
Date: Tue, 20 Dec 2022 11:55:23 +0100 [thread overview]
Message-ID: <877cymbazo.fsf@gnu.org> (raw)
In-Reply-To: <87bko64xfq.fsf@contorta> (Vagrant Cascadian's message of "Tue, 13 Dec 2022 16:54:17 -0800")
Howdy,
Vagrant Cascadian <vagrant@debian.org> skribis:
> On 2022-12-08, Christopher Baines wrote:
>> Only suggest waiting one week for review for simpler changes, wait two weeks
>> for more significant changes.
> ...
>> +Changes should be posted to @email{guix-patches@@gnu.org}. This mailing
>> +list fills the patch-tracking database (@pxref{Tracking Bugs and
>> +Patches}). It also allows patches to be picked up and tested by the
>> +quality assurance tooling; the result of that testing eventually shows
>> +up on the dashboard at
>> +@indicateurl{https://qa.guix.gnu.org/issue/@var{number}}, where
>> +@var{number} is the number assigned by the issue tracker. Leave time
>> +for a review, without committing anything (@pxref{Submitting Patches}).
>> +If you didn’t receive any reply after one week (two weeks for more
>> +significant changes), and if you're confident, it's OK to commit.
>
> My one concern here for things that I tend to work on is
> diffoscope... it has such a large dependency graph(?) because it
> supports so many file formats, it pulls in quite a lot for the test
> suites...
>
> In a week or two of changes between submission and being able to push to
> master, I'd worry that you could end up with a diffoscope that wouldn't
> build because of changes to one of it's (native-)inputs or whatnot
> because of changes to master in the previous week...
I suppose there’s always this risk. Ideally, qa.guix would either
rebuild things periodically (rebasing them) or could be told to.
> That said, overall, I think sending everything through guix-patches is a
> good change, even if my lazier self pouts a little at having to deal
> with more process for seemingly simple things. :)
Right, I can sympathize. :-) I’ve done my share of direct pushes for
“simple thing”, but I think there’s now evidence that sometimes simple
things aren’t that simple.
Waiting for a green flag from qa.guix and/or from fellow hackers might
seem annoying at first, but the gains in terms of peace of mind, smooth
collaboration, and overall stability are worth it.
Ludo’.
next prev parent reply other threads:[~2022-12-20 10:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 10:49 [bug#59513] [PATCH] doc: contributing: Tweak the Commit Policy Christopher Baines
2022-11-23 20:27 ` zimoun
2022-11-24 8:40 ` Christopher Baines
2022-11-24 11:59 ` zimoun
2022-11-28 11:46 ` Christopher Baines
2022-12-02 9:45 ` Ludovic Courtès
2022-12-01 21:44 ` Ludovic Courtès
2022-12-12 10:33 ` Christopher Baines
2022-12-12 11:47 ` Ludovic Courtès
2022-12-08 11:20 ` [bug#59513] [PATCH v2] " Christopher Baines
2022-12-08 13:53 ` Liliana Marie Prikler
2022-12-12 10:49 ` Christopher Baines
2022-12-12 20:27 ` Liliana Marie Prikler
2022-12-13 14:06 ` Christopher Baines
2022-12-14 0:54 ` Vagrant Cascadian
2022-12-14 10:21 ` Christopher Baines
2022-12-20 10:55 ` Ludovic Courtès [this message]
2022-12-17 5:01 ` [bug#59513] [PATCH] " Maxim Cournoyer
2023-01-05 9:12 ` [bug#59513] [PATCH v2] " zimoun
2023-01-11 10:48 ` Christopher Baines
2023-01-11 10:50 ` bug#59513: " Christopher Baines
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=877cymbazo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=59513@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=mail@cbaines.net \
--cc=vagrant@debian.org \
--cc=zimon.toutoune@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.