From: Suhail Singh <suhailsingh247@gmail.com>
To: Sarthak Shah <shahsarthakw@gmail.com>
Cc: "Suhail Singh" <suhailsingh247@gmail.com>,
"Marek Paśnikowski" <marek@marekpasnikowski.pl>,
"Guix Devel" <guix-devel@gnu.org>
Subject: Re: Global modification of #:make-flags
Date: Wed, 21 Aug 2024 10:37:18 -0400 [thread overview]
Message-ID: <87cym2eych.fsf@gmail.com> (raw)
In-Reply-To: <CADBZEVkWDPJsQBDGTtbWkND-ishSP54rJJvwC15=wRDvtAG_4g@mail.gmail.com> (Sarthak Shah's message of "Wed, 21 Aug 2024 12:57:47 +0530")
Sarthak Shah <shahsarthakw@gmail.com> writes:
> From my understanding, debbugs issues are meant for technical features
> or issues pending implementation, while guix-devel threads are meant
> for discussions surrounding Guix and possible features.
I am no authority on the matter, so please take what I say with a grain
of salt. However, I have seen technical discussions (on features
not-yet-fully-implemented) happen on the bug and patches mailing lists
in addition to guix-devel. I don't believe there's a strict rule. To
an extent it's to the discretion of the individual(s) having the
discussion.
Additionally, having an issue open doesn't preclude one from cc-ing
guix-devel in replies, in case that's desired. Though, whether that's
/desirable/ is a different matter.
> This is why I had linked the relevant mailing list thread in my blog post
> as well.
It's your prerogative at the end of the day, however, if you would like
others to try out the patches, you may have better luck by creating an
issue where the patch reroll count can be incremented and tracked (and
those interested can follow the progress).
--
Suhail
next prev parent reply other threads:[~2024-08-21 14:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 10:04 Global modification of #:make-flags Marek Paśnikowski
2024-08-20 10:29 ` Sarthak Shah
2024-08-20 13:13 ` Suhail Singh
2024-08-20 23:42 ` Sarthak Shah
2024-08-21 6:54 ` Suhail Singh
2024-08-21 7:27 ` Sarthak Shah
2024-08-21 14:37 ` Suhail Singh [this message]
2024-08-22 16:14 ` Sergio Pastor Pérez
2024-08-23 9:01 ` Sarthak Shah
2024-08-21 7:09 ` Marek Paśnikowski
2024-08-21 7:21 ` Sarthak Shah
2024-08-21 7:34 ` Marek Paśnikowski
2024-08-21 7:45 ` Sarthak Shah
2024-08-21 8:42 ` Marek Paśnikowski
2024-08-21 21:00 ` Ludovic Courtès
2024-09-06 16:27 ` Marek Paśnikowski
2024-08-22 16:35 ` Sergio Pastor Pérez
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=87cym2eych.fsf@gmail.com \
--to=suhailsingh247@gmail.com \
--cc=guix-devel@gnu.org \
--cc=marek@marekpasnikowski.pl \
--cc=shahsarthakw@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 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).