From: Kyle Meyer <kyle@kyleam.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, salutis@me.com, 52778@debbugs.gnu.org
Subject: bug#52778: 29.0.50; refill-mode issues in org-mode
Date: Sun, 26 Dec 2021 14:07:44 -0500 [thread overview]
Message-ID: <87czlj6v7j.fsf@kyleam.com> (raw)
In-Reply-To: <87lf08iwa4.fsf@localhost>
Ihor Radchenko writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> You are right. I do not actively watch Emacs bug tracker and I had no
>>> information about Rudolf's previous reports today.
>>
>> Did you look at them now? I meant bugs 52771 and 52772.
>
> Yes. One is fixed already.
Thanks for fixing 52772. I've marked it as done. (One way to do that
is appending -done to the bug number in the debbugs address:
<52772-done@debbugs.gnu.org>.)
> The other one should probably be forwarded to
> Org ML. However, I am not sure what is the right way to redirect
> messages from Emacs bug tracker to Org ML. Usually, Kyle takes care
> about this part.
Before replying to a message, you can reassign it the "org-mode" package
by sending a message to control@debbugs.gnu.org. Here's an example:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38592;msg=10
However, looking at <https://debbugs.gnu.org/52771>, it's already been
assigned to the org-mode package, so the reply I've sent should go to
Org's mailing list.
prev parent reply other threads:[~2021-12-26 19:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2y24aum1n.fsf@me.com>
[not found] ` <83bl16rrz6.fsf@gnu.org>
[not found] ` <87r1a2oxhm.fsf@localhost>
[not found] ` <838rwarq51.fsf@gnu.org>
[not found] ` <87o856ovtr.fsf@localhost>
2021-12-25 21:14 ` bug#52778: 29.0.50; refill-mode issues in org-mode Rudolf Adamkovič via General discussions about Org-mode.
[not found] ` <834k6yrkzg.fsf@gnu.org>
[not found] ` <87lf08iwa4.fsf@localhost>
2021-12-26 19:07 ` Kyle Meyer [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:
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=87czlj6v7j.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=52778@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=salutis@me.com \
--cc=yantar92@gmail.com \
/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).