From: Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: 45mg <45mg.writes@gmail.com>
Cc: 75145@debbugs.gnu.org, guix-devel@gnu.org
Subject: Re: [PATCH v2 0/1] services: network-manager: Add extra-configuration-files field.
Date: Thu, 09 Jan 2025 11:34:12 -0800 [thread overview]
Message-ID: <87seprdbnv.fsf@lease-up.com> (raw)
In-Reply-To: <cover.1736423822.git.45mg.writes@gmail.com> (45mg.writes@gmail.com's message of "Thu, 9 Jan 2025 12:24:30 +0000")
Hi 45mg,
On Thu, Jan 09 2025, 45mg wrote:
> this patch failed to get any attention in two weeks
Two weeks isn't a long time in free software projects. A more common
time frame would be between one year and eighteen months.
> I'm CC'ing guix-devel on this one
Pings are generally frowned upon, but I also just did it yesterday. [1]
Pings are usually not worth it anywhere, not just in GNU Guix. Pings
are likely to be ineffective in hastening the acceptance of your patch
but will almost certainly affect your social relationships negatively.
> This patch allows users to specify configuration files for NetworkManager.
If you require that change personally, as I suspect you do, my
recommendation would be to clone the Guix repo and pull your 'guix'
executable from your custom branch. For example, I have in my
channels.scm a branch that I rebase periodically. [2]
I pull with
guix pull --allow-downgrades --disable-authentication
That kind of setup totally removes the timing pressure from your
contribution. It also allows you to test your patch in real life and
then argue with committers solely about its merits. It's better for
everybody, I think.
It may leave everyone, most importantly yourself, in a happier place.
Kind regards
Felix
[1] https://lists.gnu.org/archive/html/guix-devel/2025-01/msg00056.html
[2] https://codeberg.org/lechner/guix-config/src/branch/history/channels.scm
next prev parent reply other threads:[~2025-01-09 19:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7743f403ebf1693fc386a397e9aed1975b43f900.1735323486.git.45mg.writes@gmail.com>
2025-01-09 12:24 ` [PATCH v2 0/1] services: network-manager: Add extra-configuration-files field 45mg
2025-01-09 14:44 ` [bug#75145] " Arnaud Daby-Seesaram
2025-01-09 17:03 ` 45mg
2025-01-09 19:34 ` Felix Lechner via Development of GNU Guix and the GNU System distribution. [this message]
2025-01-13 13:47 ` Attila Lendvai
2025-01-13 15:47 ` Ricardo Wurmus
2025-01-17 13:43 ` [bug#75145] " Attila Lendvai
2025-01-17 20:25 ` Ricardo Wurmus
2025-01-22 0:16 ` [bug#75145] " Attila Lendvai
2025-01-09 12:24 ` [PATCH v2 1/1] " 45mg
2025-01-12 17:43 ` [PATCH v2 0/1] " 45mg
2025-01-21 4:52 ` [bug#75145] " Maxim Cournoyer
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=87seprdbnv.fsf@lease-up.com \
--to=guix-devel@gnu.org \
--cc=45mg.writes@gmail.com \
--cc=75145@debbugs.gnu.org \
--cc=felix.lechner@lease-up.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 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).