From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: changing gnus-group-posting-charset-alist
Date: Sat, 16 Oct 2004 08:30:26 +0900 [thread overview]
Message-ID: <yotlbrf3v9t9.fsf@jpl.org> (raw)
In-Reply-To: <m3is9cdiwz.fsf@defun.localdomain>
>>>>> In <m3is9cdiwz.fsf@defun.localdomain>
>>>>> Jesper Harder <harder@ifa.au.dk> wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> What I'd like to say is: let's change the default value to:
>> (message-this-is-news nil nil)
>> WDYT?
> The posting guidelines for the dk.* hierarchy discourage CTE=QP. So
> at least for that case it's not a good change.
I see. Thanks. I'll reverse the approach. The main groups to
which Japanese articles are posted are fj and japan, and gmane.
All gmane groups allow the mail convention. So, I think I can
add the following elements as the default value.
("Regexp for fj and japan" nil nil)
("Regexp for Gmane groups" nil nil)
Is there an evil thing?
next prev parent reply other threads:[~2004-10-15 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 10:30 Katsumi Yamaoka
2004-10-15 16:51 ` Jesper Harder
2004-10-15 23:30 ` Katsumi Yamaoka [this message]
2004-10-17 23:57 ` Katsumi Yamaoka
2004-10-18 20:35 ` Jesper Harder
2004-10-19 0:51 ` Katsumi Yamaoka
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=yotlbrf3v9t9.fsf@jpl.org \
--to=yamaoka@jpl.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).