From: Christopher Baines <mail@cbaines.net>
To: Attila Lendvai <attila@lendvai.name>
Cc: attila.lendvai@gmail.com, 71858@debbugs.gnu.org
Subject: [bug#71858] [PATCH shepherd] doc: Patches should be sent to guix-patches instead of guix-devel.
Date: Tue, 09 Jul 2024 12:21:18 +0200 [thread overview]
Message-ID: <87msmq9881.fsf@cbaines.net> (raw)
In-Reply-To: <075F6Ox4m0X9Y-iJX3eBQPUf5fCDDiYS5QRcWJ0rKxJOxBJAhODLVzId_jTJigKx94R0Mgu_rqi4qztWipuXTrTR_0ZJ2lMotMrEKehN30o=@lendvai.name> (Attila Lendvai's message of "Sun, 30 Jun 2024 17:12:44 +0000")
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
Attila Lendvai <attila@lendvai.name> writes:
>> > From: Attila Lendvai attila@lendvai.name
>> >
>> > ---
>> > doc/shepherd.texi | 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>>
>> What are you looking to get from this change?
>
>
> i'm confused, so let's sync some assumptions:
>
> are you/we happy that shepherd patches end up on guix-devel?
>
> because i've just sent several shepherd patches to guix-devel, and
> when i thought about it, i wouldn't be happy to receive a storm of
> non-guix patches on guix-devel. hence my patch to the manual.
Personally, I'm happy for shepherd patches to go to guix-devel.
I don't think anyone has raised an issue with this, but if they did, I'd
suggest setting up a dedicated list for the shepherd and using that.
Maybe if the patches are for a bug, then they could be sent to the
Debbugs bug instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
prev parent reply other threads:[~2024-07-09 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 16:28 [bug#71858] [PATCH shepherd] doc: Patches should be sent to guix-patches instead of guix-devel attila.lendvai
2024-06-30 16:36 ` Christopher Baines
2024-06-30 17:12 ` Attila Lendvai
2024-07-09 10:21 ` Christopher Baines [this message]
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=87msmq9881.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=71858@debbugs.gnu.org \
--cc=attila.lendvai@gmail.com \
--cc=attila@lendvai.name \
/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).