From: Luis Felipe <sirgazil@zoho.com>
To: Rostislav Svoboda <rostislav.svoboda@gmail.com>, guix-devel@gnu.org
Cc: Christopher Baines <guix@cbaines.net>,
Nicolas Graves <ngraves@ngraves.fr>
Subject: Re: Bug triage
Date: Fri, 8 Nov 2024 16:00:25 +0000 [thread overview]
Message-ID: <03338743-dc72-4fc9-b6ba-29c7ce7c43cb@zoho.com> (raw)
In-Reply-To: <CAEtmmexScXFTmU_BLQk-q--Ws_b03hzvG0nz_xN1GaAbPqrVTg@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 938 bytes --]
Hi,
On 8/11/24 14:11, Rostislav Svoboda wrote:
> Hello,
>
> > I've tried to do some bug/patch triage yesterday and marked a bunch of
> > patches as "easy"
>
> How well does mumi, the issue tracker, support predicates?
>
> This does not work: 'tag:easy AND (NOT (is:closed OR is:done))'
> https://issues.guix.gnu.org/search?query=tag%3Aeasy+AND+%28NOT+%28is%3Aclosed+OR+is%3Adone%29%29
Isn't this the same as requesting open issues tagged "easy"? Because, if
I understand correctly, that is done by typing «tag:easy is:open»
(without the quotes):
https://issues.guix.gnu.org/search?query=is%3Aopen+tag%3Aeasy
> This works: 'tag:easy AND (is:closed OR
> is:done)'https://issues.guix.gnu.org/search?query=tag%3Aeasy+AND+%28is%3Aclosed+OR+is%3Adone%29
And this would be «tag:easy is:closed» (I think closed and done are the
same):
https://issues.guix.gnu.org/search?query=tag%3Aeasy+is%3Aclosed
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2881 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2024-11-08 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 6:23 Bug triage Nicolas Graves
2024-11-07 15:17 ` Simon Tournier
2024-11-08 14:11 ` Rostislav Svoboda
2024-11-08 15:22 ` Nicolas Graves
2024-11-08 16:00 ` Luis Felipe [this message]
2024-11-08 16:11 ` Rostislav Svoboda
2024-11-14 8:20 ` Ricardo Wurmus
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=03338743-dc72-4fc9-b6ba-29c7ce7c43cb@zoho.com \
--to=sirgazil@zoho.com \
--cc=guix-devel@gnu.org \
--cc=guix@cbaines.net \
--cc=ngraves@ngraves.fr \
--cc=rostislav.svoboda@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.