From: Tim Cross <firstname.lastname@example.org>
Subject: Re: the GNU bug tracker, use it or have something similar? Gmane might block attachments in bug reports
Date: Tue, 26 Oct 2021 08:55:19 +1100 [thread overview]
Message-ID: <email@example.com> (raw)
Uwe Brauer <firstname.lastname@example.org> writes:
> org-submit-bug-report sends an email to the org-mode mailing list. It
> turns out, that if you attach a file and later display that message on
> gmane, as I do in order to keep my email traffic in moderate numbers,
> then gmane might block that attachment.
> Now GNU emacs has a bug tracker what can be accessed via debbugs-org and
> there this problem does not appear.
> The org mailing list does have a similar bug tracker which is a bit of
> problem with such a workflow.
> Of course an alternative would be to CC the bug report to the GNU emacs
> list since org mode is also in the GNU emacs tree, but I am not sure
> whether this is a good idea.
I'm not sure which list you are referring to by "BNU emacs list" - do
you mean the emacs-devel list or the emacs bug list (same as
report-emacs-bug)? In any case, I don't think you should report bugs on
emacs-devel (when people do, they are typically asked to submit a bug
report. With respect to sending it to the emacs bug list (or using
report-emacs-bug), I think you should probably only do this when your
reporting a bug with the org mode bundled with emacs (just my opinion,
not policy of course). In any rate, any bug reported to the emacs bug
list just sits in the emacs bug tracker until someone sends it on to
this list and it gets added to the org list of bugs on orgmode.org. .
prev parent reply other threads:[~2021-10-25 22:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 14:21 the GNU bug tracker, use it or have something similar? Gmane might block attachments in bug reports Uwe Brauer
2021-10-25 17:00 ` Max Nikulin
2021-10-25 19:14 ` Uwe Brauer
2021-10-25 19:15 ` Uwe Brauer
2021-10-25 19:21 ` Uwe Brauer
2021-10-26 16:59 ` Max Nikulin
2021-10-25 21:55 ` Tim Cross [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).