From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Inaccuracy in the documentation
Date: Thu, 22 Mar 2007 21:04:08 +0900 [thread overview]
Message-ID: <b4modml1o3r.fsf@jpl.org> (raw)
In-Reply-To: <87k5x9msyz.fsf@baldur.tsdh.de>
>>>>> In <87k5x9msyz.fsf@baldur.tsdh.de> Tassilo Horn wrote:
> the first thing is that the Gnus docs state that it corresponds to No
> Gnus 0.4. I think it has to be 0.5, right?
> ,----[ (info "(gnus)Top") ]
>| This manual corresponds to No Gnus v0.4.
> `----
So is the Message info. I vote to making them synch to
`gnus-version', as well as the ones in the Emacs CVS and
the v5-10 branch. It will make releasing new versions easy.
next prev parent reply other threads:[~2007-03-22 12:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 11:13 Tassilo Horn
2007-03-22 12:04 ` Katsumi Yamaoka [this message]
2007-03-23 18:17 ` Version numbers of unreleased stable and development versions (was: Inaccuracy in the documentation) Reiner Steib
2007-05-26 8:21 ` Version numbers of unreleased stable and development versions Reiner Steib
2007-05-28 9:03 ` Didier Verna
2007-05-28 12:57 ` Zlatko Calusic
2007-05-28 17:42 ` Reiner Steib
2007-05-29 7:21 ` Didier Verna
2007-05-31 19:01 ` Reiner Steib
2007-06-04 9:29 ` Didier Verna
2007-06-13 18:50 ` Reiner Steib
2007-06-15 17:53 ` Reiner Steib
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=b4modml1o3r.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).