From: Max Nikulin <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 23:59:43 +0700 [thread overview]
Message-ID: <email@example.com> (raw)
On 26/10/2021 02:21, Uwe Brauer wrote:
> Max Nikulin writes:
>> I am unsure to which list you are going to send a copy. Emacs-orgmode
>> is hosted on gnu.org just as other emacs lists.
> To firstname.lastname@example.org
> That one I can access via debbugs-org
> That function seems a good compromise: it does not require to be
> subscribed to the list, and it does not suffer from gmane's problem.
I may be wrong in some minor details, but Emacs bug tracker (among other
GNU projects) resides on https://debbugs.gnu.org/ Its main interface
though is email, but ...@debbugs.gnu.org, not email@example.com. The
latter is just a broadcast notification channel. I do not think,
messages sent directly to firstname.lastname@example.org are forwarded to
debbugs.gnu.org. Sometimes emacs-orgmode is added as Cc address for bugs
tracked by debbugs. In such cases it is better to reply directly to mail
address associated with the bug, not to the mail list, otherwise the
response will not appear in the debbugs archive.
> When I call debbugs-org I do not see my bug, are you saying I should?
You may see your bug on https://updates.orgmode.org/ that is independent
tracker, see e.g. https://email@example.com/
However someone should confirm that it is a real bug.
Bastien. Re: issue tracker? Mon, 01 Jun 2020 16:36:59 +0200
> I'd like to keep this mailing list as the central place to discuss
> everything about Org, including bug reports.
I do not know what are the reasons why Bastien prefers to develop
"Woof!" instead of relying on much more powerful debbugs. As to me, for
some reason it requires a bit more time and cognitive efforts to realize
current status of a debbugs issue in comparison to the most of other
trackers. In addition, I do not like that GNU's debbugs instance exposes
contents to general purpose search engines in a form that makes it hard
to provide relevant search results and descriptive summary snippet (due
to some performance reasons). So bugs are often rates much lower than
reddit threads and stackexchange questions.
> Well one thing I learned is to stick to emacs -Q strictly, but I would
> like to know whether debbugs-org could access this bug?
org-submit-bug-report may act better by adding a warning that user may
expose some private information to public and by suggesting -Q if state
size is above some threshold.
-Q is mentioned in almost all sources related to bug reports, e.g.
https://orgmode.org/manual/Feedback.html (info "(org) Feedback")
debbugs-org is an interface to debbugs, but Org mostly uses mail list
directly and updates.orgmode.org, so the only way to get a bug in
debbugs-org is to send it to debbugs. It is neither forbidden nor
next prev parent reply other threads:[~2021-10-26 17:02 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 [this message]
2021-10-25 21:55 ` Tim Cross
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).