From: Michael Albinus <michael.albinus@gmx.de>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: CEDET package in Emacs bug tracker
Date: Mon, 15 Oct 2012 17:33:35 +0200 [thread overview]
Message-ID: <87d30jg374.fsf@gmx.de> (raw)
In-Reply-To: <vmwqys982e.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sun, 14 Oct 2012 15:18:01 -0400")
Glenn Morris <rgm@gnu.org> writes:
> If you can support the equivalent of this query:
>
> http://debbugs.gnu.org/cgi/pkgindex.cgi?indexon=users
>
> people will be able to browse the users and their tags.
Not possible exactly. The SOAP interface does not allow to check for
arbitrary user tags, it can only return user tags for a given user, and
bugs tagged by that user with such a user tag. See
<http://wiki.debian.org/DebbugsSoapInterface>.
I've written today a function `debbugs-get-usertag' with the following
docstring (it behaves a little bit different as the SOAP function
get_usertag):
| (debbugs-get-usertag USER &rest TAGS)
|
| Return a list of bug numbers which are tagged by USER.
|
| USER, a string, is either the email address of the user who has
| applied a user tag, or a pseudo-user like "emacs".
|
| TAGS is a list of strings applied as user tags. The returning
| list is filtered for these tags.
|
| If TAGS is nil, no bug numbers will be returned but a list of
| existing tags for USER.
|
| Example:
|
| (debbugs-get-usertag "emacs")
|
| => ("www" "solaris" "ls-lisp" "cygwin")
|
| (debbugs-get-usertag "emacs" "www" "cygwin")
|
| => (807 1223 5637)
That might be sufficient to our needs; in general USER shall be either a
package name, or a user's email address.
If we really want to get a list of all existing user tags, we must
either extend the SOAP interface, or we must parse the output of
<http://debbugs.gnu.org/cgi/pkgindex.cgi?indexon=users>. Not my primary
choice.
> I was just thinking about an explicit query of usertags, I don't think
> you need to show them in the default search list.
OK. I'll add a respective command to debbugs-gnu.el. Likely tomorrow.
Best regards, Michael.
next prev parent reply other threads:[~2012-10-15 15:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 18:18 CEDET package in Emacs bug tracker David Engster
2012-10-13 18:58 ` Glenn Morris
2012-10-13 19:05 ` David Engster
2012-10-13 19:21 ` Glenn Morris
2012-10-13 19:30 ` David Engster
2012-10-13 19:52 ` Glenn Morris
2012-10-14 10:30 ` Michael Albinus
2012-10-14 19:18 ` Glenn Morris
2012-10-15 15:33 ` Michael Albinus [this message]
2012-10-15 16:03 ` Glenn Morris
2012-10-16 18:15 ` David Engster
2012-10-17 12:48 ` Michael Albinus
2012-10-18 19:28 ` David Engster
2012-10-18 19:38 ` Michael Albinus
2012-10-18 19:49 ` David Engster
2012-10-25 9:49 ` Debbugs user tags (was: CEDET package in Emacs bug tracker) Michael Albinus
2012-10-25 19:43 ` Debbugs user tags David Engster
2012-10-13 22:15 ` CEDET package in Emacs bug tracker Glenn Morris
2012-10-14 11:29 ` David Engster
2012-10-14 19:10 ` Glenn Morris
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=87d30jg374.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=rgm@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.