emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.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 00:00:12 +0700	[thread overview]
Message-ID: <sl6nqu$t5t$1@ciao.gmane.io> (raw)
In-Reply-To: <87tuh5nq0y.fsf@mat.ucm.es>

On 25/10/2021 21:21, Uwe Brauer wrote:
> 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.

I do not see your attachment on news.gmane.io as well, but it is a rare 
problem. Mostly attachments are received correctly. Moreover, a part of 
your message is truncated. I am unsure whether there is some limit for 
message size or parser was confused by excessive white spaces (unsure 
whether the message was fully conformant). Anyway, size of "current 
state" part tells that it is unlikely *minimal* example that you tested 
with "emacs -Q". Even the part received by gmane has size of almost 300k.

> 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.

Attachment is available on
so I do not see any problem. Likely nobody explicitly confirmed your 
bug, so it did not appear on https://updates.orgmode.org/ On the other 
hand, a patch appeared quickly enough, so reasons to complain are 
unclear for me.

> 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 am unsure to which list you are going to send a copy. Emacs-orgmode is 
hosted on gnu.org just as other emacs lists. Besides lists.gnu.org it is 
archived on public inbox instances and these archives were able to parse 
your message. For issues filed through debbugs.gnu.org latency is often 
higher that for ones sent directly to this list.

Are there evidences that it was not a rare case when an attachments from 
a messages generated by org-submit-bug-report was lost by gmane and 
change of workflow is really required?

  reply	other threads:[~2021-10-25 17:01 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 [this message]
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

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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to='sl6nqu$t5t$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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).