From: Josselin Poiret <dev@jpoiret.xyz>
To: Felix Lechner <felix.lechner@lease-up.com>, guix-devel@gnu.org
Subject: Re: Bugs and Patches---or rather, bugs or patches?
Date: Sun, 03 Mar 2024 17:48:18 +0100 [thread overview]
Message-ID: <87bk7vmfcd.fsf@jpoiret.xyz> (raw)
In-Reply-To: <874jdq10mg.fsf@lease-up.com>
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
Hi Felix,
Felix Lechner via "Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org> writes:
> Hi,
>
> We track bugs and patches separately. Does the distinction serve a
> purpose? May I combine them?
What do you mean by tracking them separately and combining them?
They're on two different lists, right? I don't like the separation
between both MLs, sure, but that's it. What would be the pros/cons of
such a merge?
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2024-03-03 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 14:35 Bugs and Patches---or rather, bugs or patches? Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-03-03 16:48 ` Josselin Poiret [this message]
2024-03-04 3:09 ` 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=87bk7vmfcd.fsf@jpoiret.xyz \
--to=dev@jpoiret.xyz \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
/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).