From: Stefan Kangas <stefan@marxist.se>
To: Bastien <bzg@gnu.org>
Cc: Boruch Baum <boruch_baum@gmx.com>,
Emacs-Devel List <emacs-devel@gnu.org>
Subject: Org-mode bugs in the Emacs bug tracker (was: Re: bug archiving policy)
Date: Thu, 10 Dec 2020 07:45:08 -0600 [thread overview]
Message-ID: <CADwFkmm=SXzpKO_hFP4=gNNCnG5DA3ryv1hs4ChVO16id9LzTA@mail.gmail.com> (raw)
In-Reply-To: <87o8j1537q.fsf@bzg.fr>
Bastien <bzg@gnu.org> writes:
> Yes, I recommend sending bug reports to emacs-orgmode@gnu.org first.
I have been thinking a little bit about the org-mode bugs we currently
have in the Emacs bug tracker. In general, of course we can keep them
open if it helps and the status quo seems to work mostly fine. But it
seems like these bugs risk becoming a bit forgotten and unattended.
Perhaps we would be better off forwarding any org-mode bugs to you for
tracking instead. The alternatives I see are:
1. Reassign any such bugs to package "org-mode", which leaves them at:
https://debbugs.gnu.org/cgi/pkgreport.cgi?package=org-mode
2. Close these bugs in our tracker and forward them to
emacs-orgmode@gnu.org.
3. Leave it all alone; continue as we have been.
Do you have any preference or thoughts about the above?
(Please forgive me if this has already been discussed in the past.
I tried searching emacs-devel but couldn't find anything.)
next prev parent reply other threads:[~2020-12-10 13:45 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 ` bug archiving policy Bastien
2020-12-10 13:45 ` Stefan Kangas [this message]
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='CADwFkmm=SXzpKO_hFP4=gNNCnG5DA3ryv1hs4ChVO16id9LzTA@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=boruch_baum@gmx.com \
--cc=bzg@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).