From: Felix Lechner via <help-guix@gnu.org>
To: Suhail <suhail@bayesians.ca>
Cc: "Clément Lassieur" <clement@lassieur.org>,
"Steve George" <steve@futurile.net>,
"Guix-devel mailing list" <guix-devel@gnu.org>,
"Help-Guix mailing list" <help-guix@gnu.org>
Subject: Re: Guix Days: Patch flow discussion
Date: Mon, 05 Feb 2024 11:52:54 -0800 [thread overview]
Message-ID: <87ttmm7ko9.fsf@lease-up.com> (raw)
In-Reply-To: <65c12e7e.0c0a0220.d7729.823cSMTPIN_ADDED_BROKEN@mx.google.com>
Hi Suhail,
On Mon, Feb 05 2024, suhail@bayesians.ca wrote:
> Felix Lechner via <help-guix@gnu.org> writes:
>
> Is your position that
First off, I'm sorry I write so much today. For a project the size of
Guix, it's not good for one person to belabor a point repeatedly. I am
responding to your request for a clarification.
> 1. this never happens today and thus, should happen some times when
> warranted. Or that,
>
> 2. it happens far too rarely today, and should happen more often. Or
> that,
>
> 3. committers should never ask for revisions?
None of the above. I believe committers should commit only changes they
are comfortable with. Otherwise, they should leave a bug to folks with
more experience, perhaps tagging it along the way.
I think there should be a hundred people who do nothing but add new
packages. They would free up valuable capacity for the people
experienced with build systems, Guix services and their configuration,
the user interface, the daemon, cross-compilation and other more
difficult speciality areas.
Kind regards
Felix
next parent reply other threads:[~2024-02-05 19:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <65c12e7e.0c0a0220.d7729.823cSMTPIN_ADDED_BROKEN@mx.google.com>
2024-02-05 19:52 ` Felix Lechner via [this message]
2024-02-18 2:31 Guix Days: Patch flow discussion Suhail
[not found] <35786.5440238797$1707248619@news.gmane.org>
2024-02-16 10:56 ` Clément Lassieur
2024-02-16 11:03 ` Andreas Enge
2024-02-16 11:28 ` Clément Lassieur
2024-02-16 12:06 ` Christopher Baines
-- strict thread matches above, loose matches on Subject: below --
2024-02-06 19:47 Suhail
2024-02-06 19:42 Suhail
2024-02-05 18:51 Suhail
2024-02-06 16:51 ` Steve George
2024-02-05 9:39 Steve George
2024-02-05 15:57 ` Clément Lassieur
2024-02-05 17:10 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-02-05 17:28 ` Clément Lassieur
2024-02-05 18:27 ` Felix Lechner via
2024-02-05 18:50 ` Clément Lassieur
2024-02-05 22:10 ` Steve George
2024-02-06 13:27 ` Edouard Klein
2024-02-06 13:39 ` Steve George
2024-02-08 19:56 ` Skyler Ferris
2024-02-09 16:35 ` Edouard Klein
2024-02-09 16:46 ` Andreas Enge
2024-02-11 10:03 ` Steve George
2024-02-14 21:40 ` Simon Tournier
2024-02-28 17:51 ` Giovanni Biscuolo
2024-02-28 19:21 ` Matt
2024-02-29 15:41 ` Daniel Littlewood
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=87ttmm7ko9.fsf@lease-up.com \
--to=help-guix@gnu.org \
--cc=clement@lassieur.org \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
--cc=steve@futurile.net \
--cc=suhail@bayesians.ca \
/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).