From: Lars Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: Re: Please review Gnus bug 20670
Date: Mon, 23 Jan 2017 00:16:01 +0100 [thread overview]
Message-ID: <87mveiptxq.fsf@gnus.org> (raw)
In-Reply-To: <87poje91uq.fsf@thinkpad.rath.org> (Nikolaus Rath's message of "Sun, 22 Jan 2017 14:17:01 -0800")
Nikolaus Rath <Nikolaus@rath.org> writes:
> Is there anything I can do to move this forward?
I'll try to take a look at the Gnus backlog later this week.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2017-01-22 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 19:10 Please review Gnus bug 20670 Nikolaus Rath
2017-01-01 19:16 ` Nikolaus Rath
2017-01-22 22:17 ` Nikolaus Rath
2017-01-22 23:16 ` Lars Ingebrigtsen [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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mveiptxq.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@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.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).