From: Bastien <bzg@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Boruch Baum <boruch_baum@gmx.com>,
Emacs-Devel List <emacs-devel@gnu.org>
Subject: Re: bug archiving policy
Date: Thu, 10 Dec 2020 12:07:37 +0100 [thread overview]
Message-ID: <87o8j1537q.fsf@bzg.fr> (raw)
In-Reply-To: <CADwFkm=BnTGsqzMgEYsE9=5sQOjmumwOn0GWb9qU5mp86m_qJQ@mail.gmail.com> (Stefan Kangas's message of "Sun, 6 Dec 2020 03:52:34 -0600")
Hi,
thanks Stefan for cc'ing me.
Stefan Kangas <stefankangas@gmail.com> writes:
> Although the org-mode maintainers do read emacs-devel and bug-gnu-emacs
> with some frequency, most subscribers are not org-mode experts.
>
> I would therefore recommend sending org-mode patches directly to the
> org-mode mailing list: emacs-orgmode@gnu.org. This makes sure it is
> seen by the competent and helpful org-mode hackers. In most cases, I
> don't think there is any need to also open a bug against Emacs.
Yes, I recommend sending bug reports to emacs-orgmode@gnu.org first.
Note that we keep track on them here: https://updates.orgmode.org
--
Bastien
next prev parent reply other threads:[~2020-12-10 11:07 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 9:26 bug archiving policy Boruch Baum
2020-12-06 9:52 ` Stefan Kangas
2020-12-06 10:14 ` Boruch Baum
2020-12-06 10:24 ` Jean Louis
2020-12-10 11:08 ` Bastien
2020-12-10 11:23 ` Stefan Kangas
2020-12-10 14:21 ` Eli Zaretskii
2020-12-11 5:53 ` Bastien
2020-12-06 10:18 ` Jean Louis
2020-12-10 11:10 ` Bastien
2020-12-10 11:57 ` Jean Louis
2020-12-11 5:58 ` Bastien
2020-12-12 5:40 ` Jean Louis
2020-12-12 13:44 ` Stefan Monnier
2020-12-13 9:48 ` Bastien
2020-12-13 16:00 ` Michael Albinus
2020-12-13 16:30 ` Bastien
2020-12-13 18:00 ` Michael Albinus
2020-12-13 17:09 ` Org-mode in debbugs [was Re: bug archiving policy] Glenn Morris
2020-12-13 17:58 ` Michael Albinus
2020-12-10 11:07 ` Bastien [this message]
2020-12-10 13:45 ` Org-mode bugs in the Emacs bug tracker (was: Re: bug archiving policy) Stefan Kangas
2020-12-11 5:36 ` Org-mode bugs in the Emacs bug tracker Bastien
2020-12-11 13:11 ` Stefan Kangas
2020-12-11 21:47 ` Tim Cross
2020-12-11 23:53 ` Bastien
2020-12-12 1:46 ` Tim Cross
2020-12-12 5:11 ` Jean Louis
2020-12-13 9:41 ` Bastien
2020-12-11 23:45 ` Bastien
2020-12-12 5:42 ` Jean Louis
2020-12-06 9:56 ` bug archiving policy Eli Zaretskii
2020-12-06 10:18 ` Boruch Baum
2020-12-06 10:24 ` Eli Zaretskii
2020-12-06 10:39 ` Boruch Baum
2020-12-06 10:57 ` Eli Zaretskii
2020-12-06 11:13 ` Boruch Baum
2020-12-06 11:22 ` Michael Albinus
2020-12-06 11:28 ` Boruch Baum
2020-12-06 10:21 ` Boruch Baum
2020-12-06 10:52 ` Eli Zaretskii
2020-12-06 11:09 ` Stefan Kangas
2020-12-06 11:18 ` Boruch Baum
2020-12-06 11:25 ` Michael Albinus
2020-12-06 11:30 ` Boruch Baum
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=87o8j1537q.fsf@bzg.fr \
--to=bzg@gnu.org \
--cc=boruch_baum@gmx.com \
--cc=emacs-devel@gnu.org \
--cc=stefankangas@gmail.com \
/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).