From: Michael Albinus <michael.albinus@gmx.de>
To: emacs-devel@gnu.org
Cc: "Lars Magne Ingebrigtsen" <larsi@gnus.org>,
"Andreas Röhler" <andreas.roehler@online.de>,
"Nicolas Petton" <nicolas@petton.fr>,
"Dmitry Gutov" <dgutov@yandex.ru>
Subject: Re: Seeking a "Patch Champion"
Date: Tue, 03 May 2016 09:58:57 +0200 [thread overview]
Message-ID: <877ffbo9mm.fsf@gmx.de> (raw)
In-Reply-To: <m2zis8tc1t.fsf@newartisans.com> (John Wiegley's message of "Mon, 02 May 2016 13:55:26 -0700")
John Wiegley <jwiegley@gmail.com> writes:
> Lars, can you extend debbugs to scan for patches that aren't mentioned by
> having [PATCH] in the subject line, both for attachments and for inline
> patches?
M-x debbugs-gnu-search <RET> [RX] ^@@ <RET> package <RET> emacs <RET> <RET>
This returns you all Emacs bugs which have message containing a patch
line starting with "@@". Unfortunately, it returns *all* bugs, even the
closed and/or archived ones (2789 as of today). This is unfortune. You
could filter out the closed bugs by typing "x" (351 bugs are left), but
this is bad wrt performance and load on the debbugs server.
The debbugs interface offers also the attribute "status" with the value
"open", which should discriminate the results to still active bugs. That
doesn't seem to work. Will investigate what's up.
If the interactive command shown above looks useful, I could provide a
function doing the same.
Best regards, Michael.
next prev parent reply other threads:[~2016-05-03 7:58 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 21:22 Seeking a "Patch Champion" John Wiegley
2016-04-23 21:45 ` Dmitry Gutov
2016-04-23 21:54 ` John Wiegley
2016-04-25 19:50 ` Dmitry Gutov
2016-04-25 19:59 ` Dmitry Gutov
2016-04-25 21:29 ` John Wiegley
2016-04-25 21:35 ` Dmitry Gutov
2016-04-26 14:27 ` John Wiegley
2016-04-25 11:29 ` Nicolas Petton
2016-04-25 17:37 ` John Wiegley
2016-04-25 18:48 ` Nicolas Petton
2016-04-25 19:17 ` John Wiegley
2016-04-25 19:28 ` John Wiegley
2016-04-25 16:40 ` Lars Magne Ingebrigtsen
2016-04-25 18:11 ` Karl Fogel
2016-04-25 18:14 ` Lars Magne Ingebrigtsen
2016-04-25 19:22 ` Karl Fogel
2016-04-25 19:51 ` Dmitry Gutov
2016-04-25 20:27 ` Dmitry Gutov
2016-04-25 20:37 ` Lars Magne Ingebrigtsen
2016-04-25 20:51 ` Dmitry Gutov
2016-04-25 21:14 ` Lars Magne Ingebrigtsen
2016-04-25 21:34 ` John Wiegley
2016-04-25 22:04 ` Lars Magne Ingebrigtsen
2016-04-25 23:44 ` Lars Magne Ingebrigtsen
2016-04-26 6:32 ` Andreas Röhler
2016-04-26 14:30 ` John Wiegley
2016-04-26 15:04 ` Nicolas Petton
2016-04-26 20:24 ` Dmitry Gutov
2016-04-26 21:01 ` John Wiegley
2016-04-27 6:16 ` Eli Zaretskii
2016-04-27 14:40 ` Lars Magne Ingebrigtsen
2016-04-27 15:31 ` Nicolas Petton
2016-04-27 15:49 ` Lars Ingebrigtsen
2016-05-02 7:55 ` Nicolas Petton
2016-05-02 20:55 ` John Wiegley
2016-05-02 21:54 ` Lars Ingebrigtsen
2016-05-03 7:58 ` Michael Albinus [this message]
2016-04-28 19:30 ` Philipp Stephani
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=877ffbo9mm.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=andreas.roehler@online.de \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=nicolas@petton.fr \
/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/emacs.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).