From: David Engster <deng@randomsample.de>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Bastien <bzg@altern.org>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: bug-tracker
Date: Fri, 22 Feb 2013 21:45:52 +0100 [thread overview]
Message-ID: <87d2vs5b7j.fsf@engster.org> (raw)
In-Reply-To: <87ip5k3xfg.fsf@gmx.de> (Michael Albinus's message of "Fri, 22 Feb 2013 21:28:51 +0100")
Michael Albinus writes:
> David Engster <deng@randomsample.de> writes:
>
>> Is it OK to report bugs for upstream/development versions through
>> `report-emacs-bugs', though? I always thought this should only be used
>> for stuff that's actually bundled with Emacs (what about bugs in
>> org/contrib, for instance?).
>
> debbugs.gnu.org is not only for Emacs. See
> <http://debbugs.gnu.org/db/ix/packages.html> which other projects are
> hosted there. "gnus" is a prominent example for a subpackage of Emacs
> with an own bug package using debbugs.gnu.org.
>
> An alternative approach is tagging bugs of a project with your package
> name. See existing user tags of project emacs at
> <http://debbugs.gnu.org/cgi/pkgindex.cgi?indexon=usertag;user=emacs>. "cedet"
> uses this mechanism already.
I know. I'm the guy who started using those tags for CEDET. :-)
I was always under the impression that those tags are merely a way for,
well, tagging bugs, so that you can search for them. Same for
packages. I didn't know that this also implied that you're encouraged to
report bugs against upstream packages, possibly for features which are
not yet in Emacs (or may even never land there, like some stuff in
org/contrib, cedet/contrib, etc.).
-David
next prev parent reply other threads:[~2013-02-22 20:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 13:36 bug-tracker Andreas Röhler
2013-02-22 14:52 ` bug-tracker Michael Albinus
2013-02-22 19:56 ` bug-tracker Andreas Röhler
2013-02-22 20:09 ` bug-tracker Michael Albinus
2013-02-22 21:23 ` bug-tracker Andreas Röhler
2013-02-23 7:39 ` bug-tracker Michael Albinus
2013-02-23 8:09 ` bug-tracker Andreas Röhler
2013-02-26 16:24 ` bug-tracker Bastien
2013-02-22 20:10 ` bug-tracker Yagnesh Raghava Yakkala
2013-02-22 21:09 ` bug-tracker Andreas Röhler
2013-02-22 20:50 ` bug-tracker Suvayu Ali
2013-02-22 21:13 ` bug-tracker Andreas Röhler
2013-02-25 15:51 ` bug-tracker Sebastien Vauban
2013-02-26 6:47 ` bug-tracker Andreas Röhler
2013-02-22 20:15 ` bug-tracker David Engster
2013-02-22 20:28 ` bug-tracker Michael Albinus
2013-02-22 20:45 ` David Engster [this message]
2013-02-23 7:36 ` bug-tracker 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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d2vs5b7j.fsf@engster.org \
--to=deng@randomsample.de \
--cc=bzg@altern.org \
--cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).