From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Felix Lechner via "Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org>
Cc: Simon Tournier <zimon.toutoune@gmail.com>,
Felix Lechner <felix.lechner@lease-up.com>
Subject: Re: Greater bug specifics for automatic team assignment
Date: Mon, 01 May 2023 11:38:35 -0400 [thread overview]
Message-ID: <87wn1s3vus.fsf@gmail.com> (raw)
In-Reply-To: <CAFHYt56H-SqwVdh3BTtS_HosJxLG4fAN1Bxyt5+Lx8drFiNv=w@mail.gmail.com> (Felix Lechner via's message of "Fri, 28 Apr 2023 10:29:11 -0700")
Hi Felix,
Felix Lechner via "Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org> writes:
> Hi Simon,
>
> On Fri, Apr 28, 2023 at 10:02 AM Simon Tournier
> <zimon.toutoune@gmail.com> wrote:
>>
>> What do you have in mind?
>
> In my recollection of using Debbugs in Debian, which uses a slightly
> different version with more features (for example, a SOAP interface)
> than the instance provided by GNU.org, there is a feature called "user
> tags." They allow anyone to set arbitrary labels. [1]
The GNU Debbugs also has the user tags feature (it's documented in our
manual, as was pointed by Simon).
I haven't found how it's supposed to work exactly, as when adding test
tags to some issues, I can't seem to find them back. Perhaps you could
teach us how you used them, perhaps improving the doc already mentioning
their usage in the Guix manual? That'd be cool.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-05-01 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 20:57 Greater bug specifics for automatic team assignment Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-04-28 14:48 ` Simon Tournier
2023-04-28 17:29 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-05-01 15:38 ` Maxim Cournoyer [this message]
2023-04-28 23:05 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wn1s3vus.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.