From: Michael Albinus <michael.albinus@gmx.de>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: Bastien <bzg@altern.org>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: bug-tracker
Date: Sat, 23 Feb 2013 08:36:34 +0100 [thread overview]
Message-ID: <87zjyv32il.fsf@gmx.de> (raw)
In-Reply-To: <87d2vs5b7j.fsf@engster.org> (David Engster's message of "Fri, 22 Feb 2013 21:45:52 +0100")
David Engster <deng@randomsample.de> writes:
> 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.).
This must be discussed with the Emacs maintainers, of course. If org
error reports will contain a substantial part of non-core Emacs
problems, an own debbugs package "org" might be better. Reports arriving
via the Emacs report chain could be reassigned to both packages
"emacs,org" then.
I recommend to contact Glenn Morris.
> -David
Best regards, Michael.
prev parent reply other threads:[~2013-02-23 7:36 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 ` bug-tracker David Engster
2013-02-23 7:36 ` Michael Albinus [this message]
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=87zjyv32il.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=andreas.roehler@easy-emacs.de \
--cc=bzg@altern.org \
--cc=emacs-orgmode@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/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).