From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Cc: Hiroshi Fujishima <pooh@nature.tsukuba.ac.jp>
Subject: Re: typo in gnus.texi
Date: Tue, 03 Feb 2004 19:42:30 +0100 [thread overview]
Message-ID: <v9k734xaw9.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <7cvfmo9ivg.fsf@nature.tsukuba.ac.jp>
On Tue, Feb 03 2004, Hiroshi Fujishima wrote:
> I found a typo in gnus.texi.
[...]
> @example
> #!/bin/sh
> -emacs -batch -l ~/.emacs -f -l ~/.gnus.el gnus-agent-batch >/dev/null 2>&1
> +emacs -batch -l ~/.emacs -l ~/.gnus.el -f gnus-agent-batch >/dev/null 2>&1
> @end example
Thanks. Fixed in CVS.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2004-02-03 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 17:24 Hiroshi Fujishima
2004-02-03 18:42 ` Reiner Steib [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-10-19 8:47 Typo " Norbert Koch
2000-08-13 19:44 Norbert Koch
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=v9k734xaw9.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=pooh@nature.tsukuba.ac.jp \
--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).