unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Attila Lendvai <attila@lendvai.name>
To: Christopher Baines <mail@cbaines.net>
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: Sun, 30 Jun 2024 17:12:44 +0000	[thread overview]
Message-ID: <075F6Ox4m0X9Y-iJX3eBQPUf5fCDDiYS5QRcWJ0rKxJOxBJAhODLVzId_jTJigKx94R0Mgu_rqi4qztWipuXTrTR_0ZJ2lMotMrEKehN30o=@lendvai.name> (raw)
In-Reply-To: <87a5j2bd72.fsf@cbaines.net>

> > 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 think being able to assume that patches sent to
> guix-patches are for guix is helpful, e.g. some of the automated tooling
> depends on this assumption.


i don't know enough about the infrastructure, and i don't have a strong opinion about where to send this. it just felt wrong to send it to guix-devel, and then guix-patches sounded at least a little better. that's all. i'm open for other suggestions, including that the status quo is fine.

-- 
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“It requires a great deal of physical tension and mental energy to hold back feelings and memories. This energy can lead to chronic tension, headaches, aches and pains and many other physical problems. It also keeps the body in a heightened state of stress and makes people more vulnerable to anxiety, panic attacks, illness & injury.”
	— Carolyn Ainscough & Kay Toon, 'Surviving Childhood Sexual Abuse'





  reply	other threads:[~2024-06-30 17:13 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 [this message]
2024-07-09 10:21     ` 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

  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='075F6Ox4m0X9Y-iJX3eBQPUf5fCDDiYS5QRcWJ0rKxJOxBJAhODLVzId_jTJigKx94R0Mgu_rqi4qztWipuXTrTR_0ZJ2lMotMrEKehN30o=@lendvai.name' \
    --to=attila@lendvai.name \
    --cc=71858@debbugs.gnu.org \
    --cc=attila.lendvai@gmail.com \
    --cc=mail@cbaines.net \
    /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).