all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Jean Louis <bugs@gnu.support>, Boruch Baum <boruch_baum@gmx.com>,
	emacs-devel@gnu.org, Bastien <bzg@gnu.org>,
	Stefan Kangas <stefankangas@gmail.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Org-mode in debbugs [was Re: bug archiving policy]
Date: Sun, 13 Dec 2020 12:09:33 -0500	[thread overview]
Message-ID: <k07dpl8wfm.fsf_-_@fencepost.gnu.org> (raw)
In-Reply-To: <87im9566hr.fsf@gmx.de> (Michael Albinus's message of "Sun, 13 Dec 2020 17:00:32 +0100")

Michael Albinus wrote:

>>> Also we can ask debbugs to forward all `org`-tagged bug info to the
>>> orgmode mailing-list.
>>
>> Yes, I would welcome this move too.
>
> I have added org-mode now as first class citizen to debbugs.gnu.org, see
> <https://debbugs.gnu.org/Packages.html>. Could you pls send some test
> data (aka test bugs) in order to check that it works as expected?
>
> I have also used emacs-orgmode@gnu.org as maintainer address. This must
> not be wrong, but if you have another preference ...

?

Please note that this has been in place for about a decade already.
Ie, there already was an org-mode entry in /etc/debbugs/Maintainers.
Now there are two...

Ref eg https://lists.gnu.org/archive/html/emacs-orgmode/2011-10/msg00253.html

In case people are confused about how this works:

1. Sending to submit@debbugs with package org-mode sends the report to the
org mode list (since about 2010).

2. If an existing bug is reassigned to org-mode, all future
correspondence goes to the org mode list. (But the act of reassigning
does not trigger a notification mail to that list. So reassign, then
send a followup mail.)

See c-submit-bug-report for a way to integrate into a bug reporting
command.



  parent reply	other threads:[~2020-12-13 17:09 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                   ` Glenn Morris [this message]
2020-12-13 17:58                     ` Org-mode in debbugs [was Re: bug archiving policy] Michael Albinus
2020-12-10 11:07   ` bug archiving policy Bastien
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=k07dpl8wfm.fsf_-_@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=boruch_baum@gmx.com \
    --cc=bugs@gnu.support \
    --cc=bzg@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=monnier@iro.umontreal.ca \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.