emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: bug-tracker: How to response/subscribe to a bug-thread
Date: Thu, 10 Mar 2022 19:31:08 +0700	[thread overview]
Message-ID: <t0cr2d$5fp$1@ciao.gmane.io> (raw)
In-Reply-To: <16ddd39649a56bc75d396225ede37ebf@posteo.de>

On 09/03/2022 23:46, c.buhtz@posteo.jp wrote:
> There is a known bug that is also tracked on the "dashboard" 
> (https://updates.orgmode.org/) as "Inconsistent handling of id: links to 
> other file during publish".
> https://list.orgmode.org/12368452.sVpYeFqCzH@pluto/
> I was not subscribed to the list when this thread comes up. So I have no 
> mail here I can reply-to. I can I answer to that thread?

There is a number of various mail list archives that allow to fetch 
particular message and to compose a reply to it. There are some minor 
bugs (they usually have workarounds), so I can not tell that it works 
really smooth.

Besides already mentioned public inbox instance:

Gmane archive is available though news:// or nntp:// protocols. You may 
setup a news reader, subscribe to the news group and fetch old messages 
or just access particular one by its Message-ID

     w3m -m 'nntp://news.gmane.io/12368452.sVpYeFqCzH@pluto'
     w3m -m 

"Official" (GNU) mail list archive has a reply button
but it is necessary to edit "To" field otherwise the response will be 
sent off-list to the author only. Unfortunately the In-Reply-To field of 
mailto: links there violates "RFC 6068 - The 'mailto' URI Scheme" due to 
missed angle brackets around Message-ID, so a mailer may skip it.

For bugs submitted to https://debbugs.gnu.org it is enough to keep 
subject with bug number when the message is sent to 
bug-gnu-emacs@gnu.org or to send it to the mail address of the bug 
NNN@debbugs.gnu.org. Some efforts are required when you are at the HTML 
page with discussion of the bug and you intention is to respond namely 
with proper In-Reply-To. Unlike upstream https://bugs.debian.org/ , GNU 
version does not have "reply" links. It is possible to fetch particular 
message ("mbox" link), open it, and reply. Obstacles are ".mbox" 
extension instead of ".eml" despite correct MIME type "message/rfc866" 
in HTTP headers and necessity to edit "To" field since the downloaded 
message has only low-level service mail addresses.

So some attention is required to compose a well-formed response, but 
being subscribed to the mail list in advance is not a prerequisite.

      parent reply	other threads:[~2022-03-10 12:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 16:46 bug-tracker: How to response/subscribe to a bug-thread c.buhtz
2022-03-09 20:38 ` Russell Adams
2022-03-09 23:12 ` Kyle Meyer
2022-03-10 12:31 ` Max Nikulin [this message]

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='t0cr2d$5fp$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).