From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: nnrss group doesn't wash multipart article correctly
Date: Thu, 11 Dec 2008 12:21:57 -0600 [thread overview]
Message-ID: <8663lqtvwa.fsf@lifelogs.com> (raw)
In-Reply-To: <86ljupylnu.fsf@lifelogs.com>
On Tue, 09 Dec 2008 17:27:17 -0600 Ted Zlatanov <tzz@lifelogs.com> wrote:
TZ> Should I:
TZ> a) implement something for `G c' that will let users add treatments to a
TZ> group/topic, or
TZ> b) add examples to the manual of how to do the above, or
TZ> c) both (including a `G c' reference in the manual node)?
...any opinions? I hate to write and support things no one needs... If
I'm the only one who had trouble with this (or needed it at all), the
manual seems like the only place that needs a minor addition to
illustrate the customization.
Ted
next prev parent reply other threads:[~2008-12-11 18:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 21:50 Ted Zlatanov
2008-12-09 22:25 ` Adam Sjøgren
2008-12-09 23:27 ` Ted Zlatanov
2008-12-11 18:21 ` Ted Zlatanov [this message]
2008-12-11 20:02 ` Adam Sjøgren
2008-12-11 20:55 ` Reiner Steib
2008-12-12 21:51 ` Ted Zlatanov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8663lqtvwa.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).