From: Russell Adams <RLAdams@adamsinfoserv.com>
To: emacs-orgmode@gnu.org
Subject: Re: bug-tracker: How to response/subscribe to a bug-thread
Date: Wed, 9 Mar 2022 21:38:40 +0100 [thread overview]
Message-ID: <YikQUFtQ2c/5u/X+@tahm.private> (raw)
In-Reply-To: <16ddd39649a56bc75d396225ede37ebf@posteo.de>
On Wed, Mar 09, 2022 at 04:46:25PM +0000, c.buhtz@posteo.jp wrote:
> Hello,
> I still try to become warm with the bug-tracking-system you are using.
>
> 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?
On that list page, the footer says you can either download an mbox
archive of the messages and reply inside your mail client, and it
provides a link where you can use a in-reply-to and subject header
which CC's the list.
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
mailto:inkbottle007%40gmail.com?In-Reply-To=%3C12368452.sVpYeFqCzH@pluto%3E&Cc=emacs-orgmode%40gnu.org&Subject=Re%3A%20Internal%20link%20broken%20when%20publishing%20%28was%20org-id%20with%20ox-html%29
> Side question: I can I monitor that thread/bug without being subscribed
> to the list? The "dashboard" seems not to have any subscribe, monitor or
> feed mechanism. The "Atom" feed (https://list.orgmode.org/new.atom) is
> only for complete list not for one thread.
The best way is to subscribe to the list.
------------------------------------------------------------------
Russell Adams RLAdams@AdamsInfoServ.com
PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
next prev parent reply other threads:[~2022-03-09 20:39 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 [this message]
2022-03-09 23:12 ` Kyle Meyer
2022-03-10 12:31 ` Max Nikulin
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
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=YikQUFtQ2c/5u/X+@tahm.private \
--to=rladams@adamsinfoserv.com \
--cc=emacs-orgmode@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).