unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
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 02:54:48 -0400	[thread overview]
Message-ID: <87frqy4b7r.fsf@gmail.com> (raw)
In-Reply-To: <CADBZEV=gKiSyNWcx1Fs_vYZYee3eK1=b8W70Bx7-Q9rU73ivFQ@mail.gmail.com> (Sarthak Shah's message of "Wed, 21 Aug 2024 05:12:28 +0530")

Sarthak Shah <shahsarthakw@gmail.com> writes:

> I think starting a debbugs issue could be a good idea once everyone's
> onboard with getting this patch merged!

I'm not sure I agree that consensus has to be a pre-requisite for
creating an issue.

> Right now, from what I gather, there are some more important conversations
> to be had, mainly with the Guix maintainers, as merging this patch could
> lead to a sharp, unexpected increase in complexity if we do not have proper
> guidelines and procedures in place for parameterization.

Creation of an issue doesn't imply that the patch (series) has to be
merged (in its current form or otherwise).  On the other hand, creation
of an issue allows for feedback to be gathered in one place.  In fact, I
would argue that there's value in creating an issue even before any code
towards a patch has been written (by, say, submitting a feature request
to <bug-guix@gnu.org>).

If not on an issue, where do you intend to have the conversations you
alluded to above?

-- 
Suhail


  reply	other threads:[~2024-08-21  6:55 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 [this message]
2024-08-21  7:27         ` Sarthak Shah
2024-08-21 14:37           ` Suhail Singh
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=87frqy4b7r.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).