From: Joshua Branson <jbranso@dismail.de>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Use Debbugs to search for only open bugs
Date: Wed, 10 Aug 2022 11:17:19 -0400 [thread overview]
Message-ID: <87pmh8p1q8.fsf@dismail.de> (raw)
In-Reply-To: <877d3gfbks.fsf@gmx.de> (Michael Albinus's message of "Wed, 10 Aug 2022 15:54:43 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
> Michael Albinus <michael.albinus@gmx.de> writes:
>
> Hi Joshua,
>
> Well, I found the time now to check what's up.
>
>> Hmm, looks like there's an error in debbugs-gnu-search. I'll check, but
>> perhaps you might write a bug report about. I don't know whether I can
>> handle it just now, due to time constraints.
>
> There's indeed an error. The "status" attribute, when there is non-empty
> query string, must be "pending" instead of "open". And it is mapped
> internally to the attribute "pending".
>
> All this shouldn't worry you. I've just pushed debbugs 0.33, which will appear
> in a couple of hours on GNU ELPA. For the time being, you can apply
>
> (debbugs-gnu-search "wterm" '((pending . "pending")) nil '("guix" "guix-patches"))
>
> If you want to see only closed bugs, then call
>
> (debbugs-gnu-search "wterm" '((pending . "done")) nil '("guix" "guix-patches"))
>
> And if you want to see all bugs with this search string, there is
>
> (debbugs-gnu-search "wterm" nil nil '("guix" "guix-patches"))
>
> Best regards, Michael.
>
Thanks for getting back to me so quickly and for so quickly applying a
fix!
Joshua
next prev parent reply other threads:[~2022-08-10 15:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 19:40 Use Debbugs to search for only open bugs Joshua Branson
2022-08-05 1:25 ` Michael Heerdegen
2022-08-05 7:08 ` Michael Albinus
2022-08-05 8:55 ` Joshua Branson
2022-08-05 9:46 ` Michael Albinus
2022-08-10 13:54 ` Michael Albinus
2022-08-10 15:17 ` Joshua Branson [this message]
2022-08-10 15:25 ` Joshua Branson
2022-08-10 16:23 ` Michael Albinus
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmh8p1q8.fsf@dismail.de \
--to=jbranso@dismail.de \
--cc=help-gnu-emacs@gnu.org \
--cc=michael.albinus@gmx.de \
/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.
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).