From: Nikolaus Rath <Nikolaus@rath.org>
To: emacs-devel@gnu.org
Subject: Please review Gnus bug 20670
Date: Sun, 01 Jan 2017 11:10:19 -0800 [thread overview]
Message-ID: <87eg0megv8.fsf@vostro.rath.org> (raw)
Hello,
Could someone take a look at the Gnus patch in
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=20670?
The patch has been sitting there for more than a year. It would be great
to either see it committed, or to have some feedback on the issues that
prevent that.
I've been using the patch locally ever since writing it and did not
encounter any problems.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
next reply other threads:[~2017-01-01 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 19:10 Nikolaus Rath [this message]
2017-01-01 19:16 ` Please review Gnus bug 20670 Nikolaus Rath
2017-01-22 22:17 ` Nikolaus Rath
2017-01-22 23:16 ` Lars Ingebrigtsen
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=87eg0megv8.fsf@vostro.rath.org \
--to=nikolaus@rath.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).