From: despen@verizon.net
To: info-gnus-english@gnu.org
Subject: Re: author of post and signature problems
Date: Tue, 28 Dec 2010 20:49:01 -0500 [thread overview]
Message-ID: <icr5d1z6uq.fsf@verizon.net> (raw)
In-Reply-To: <mailman.0.1293579503.26585.info-gnus-english@gnu.org>
prad <prad@towardsfreedom.com> writes:
> despen@verizon.net writes:
>
>> Not only do you get around reasonable conventions, but
>> your sig gets copied into replies and avoids GNUS attempts to
>> highlight your sig correctly.
>>
> this is a very good point which hadn't occurred to me. thank you.
> i understand the newsgroup rationale thanks to your demonstration despen
> and as i explore gnus further. i am happy to comply.
Bravo, in my estimation, you're a man among men.
One who listens to contrary opinions and accepts some of them.
Good form.
next prev parent reply other threads:[~2010-12-29 1:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.31.1293525612.2341.info-gnus-english@gnu.org>
2010-12-28 10:21 ` Massimo Gengarelli
2010-12-28 14:36 ` Adam Sjøgren
2010-12-28 18:12 ` prad
[not found] ` <mailman.7.1293559906.18542.info-gnus-english@gnu.org>
2010-12-28 19:06 ` Adam Sjøgren
2010-12-28 20:19 ` prad
[not found] ` <mailman.3.1293567513.3661.info-gnus-english@gnu.org>
2010-12-28 21:25 ` Adam Sjøgren
2010-12-29 14:48 ` Philipp Haselwarter
2010-12-30 19:13 ` prad
2010-12-28 19:11 ` Richard Riley
2010-12-28 20:10 ` prad
[not found] ` <mailman.2.1293566991.3661.info-gnus-english@gnu.org>
2010-12-28 20:31 ` Richard Riley
2010-12-28 21:40 ` despen
2010-12-28 23:39 ` prad
[not found] ` <mailman.0.1293579503.26585.info-gnus-english@gnu.org>
2010-12-29 1:49 ` despen [this message]
2010-12-29 7:12 ` prad
2010-12-28 20:18 ` David Brown
2010-12-28 20:32 ` Richard Riley
2010-12-31 0:59 ` Brett Viren
2010-12-28 8:33 prad
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=icr5d1z6uq.fsf@verizon.net \
--to=despen@verizon.net \
--cc=info-gnus-english@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.
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).