From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: "replying" to my own messages
Date: Thu, 04 Sep 2003 23:09:14 +0200 [thread overview]
Message-ID: <v9k78odzwl.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <r774qzs728a.fsf@brouilly.inria.fr>
On Thu, Sep 04 2003, James Leifer wrote:
> I don't mean to be a pedant but those man pages (for 5.10.2) don't
> clearly explain what followup means (neither for news or mail):
The term "followup" is not Gnus specific and obviously it would make
no sense to explain it everywhere it appears in the manual. Therefor,
we have the node "Terminology" where many terms are explained. You
can also find that node, when looking up "followup" in the Index:
,----[ (info "(gnus)Index") ]
| * follow up: Terminology.
| * followup: Composing Messages.
`----
,----[ (info "(gnus)Terminology") ]
| "follow up"
| Post an article to the current newsgroup responding to the article
| you are reading.
`----
What do you think? Feel free to suggest improvements!
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2003-09-04 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <r77he3szxut.fsf@brouilly.inria.fr>
2003-09-04 10:50 ` Norbert Koch
2003-09-04 11:46 ` James Leifer
2003-09-04 12:45 ` Norbert Koch
[not found] ` <v9r82wfpv0.fsf@marauder.physik.uni-ulm.de>
[not found] ` <vz1xuwtqxu.fsf@redqueen.bytechase.cx>
[not found] ` <v9ekywfo15.fsf@marauder.physik.uni-ulm.de>
2003-09-04 17:50 ` Norbert Koch
[not found] ` <wwekyw1x38.fsf@eliud.mi.uib.no>
[not found] ` <r77y8x4vdbj.fsf@brouilly.inria.fr>
[not found] ` <86bru07g7t.fsf@doze.rijnh.nl>
[not found] ` <r77ptigvbc0.fsf@brouilly.inria.fr>
[not found] ` <v9iso8fpoa.fsf@marauder.physik.uni-ulm.de>
2003-09-04 20:00 ` James Leifer
2003-09-04 21:09 ` Reiner Steib [this message]
2003-09-22 22:19 ` Kai Grossjohann
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=v9k78odzwl.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).