From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: CEDET package in Emacs bug tracker
Date: Sat, 13 Oct 2012 14:58:09 -0400 [thread overview]
Message-ID: <1obog6i4hq.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <877gquck2s.fsf@engster.org> (David Engster's message of "Sat, 13 Oct 2012 20:18:03 +0200")
David Engster wrote:
> I find it difficult to search for bugs related to CEDET in the bug
> tracker. I usually search for 'semantic', 'cedet', 'srecode' and
> similar, but that's cumbersome and I also probably miss some.
>
> It'd be nice if that could be improved. Maybe CEDET could become a
> package, like Gnus or cc-mode?
Sure, you can have that if you have a dedicated mailing list for CEDET
bug reports. That's why those other packages exist; they correspond to
bug-cc-mode@gnu.org and bugs@gnus.org. If you don't, I would suggest
simply retitling bugs to include "cedet", or using usertags, rather than
a package.
But it doesn't magically make things better. Someone (usually me) has to
manually assign things to the right package. And of course I just start
by doing the kind of search that you have already done.
next prev parent reply other threads:[~2012-10-13 18:58 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 [this message]
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
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
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=1obog6i4hq.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@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 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).