From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: CVS update of gnus/texi (ChangeLog auth.texi)
Date: Mon, 13 Apr 2009 08:10:29 +0900 [thread overview]
Message-ID: <b4mhc0ttqmy.fsf@jpl.org> (raw)
In-Reply-To: <87r600wf2n.fsf@marauder.physik.uni-ulm.de>
>>>>> Reiner Steib wrote:
> On Fri, Apr 10 2009, Katsumi Yamaoka wrote:
>>> Modified: ChangeLog auth.texi
> [...]
>> There are some oddities now in auth.texi in No Gnus; e.g. two
>> @settitle lines, two @direntry sections, and `@end tex' w/o @tex.
>> The easiest way to fix them is to copy the one in Emacs to No Gnus,
>> isn't it?
> There's on line that needs to be different:
> In Gnus: @setfilename auth.info
> In Emacs: @setfilename ../../info/auth
Ok. I've synch'd up the No Gnus version with Emacs except for
that line. Now the Info file name is "auth", not "auth.info",
that follows the No Gnus convention.
Regards,
next prev parent reply other threads:[~2009-04-12 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1LsCN3-0005Oo-00@quimby.gnus.org>
2009-04-10 15:35 ` Katsumi Yamaoka
2009-04-10 18:15 ` Reiner Steib
2009-04-12 23:10 ` Katsumi Yamaoka [this message]
2009-04-13 15:53 ` Ted Zlatanov
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=b4mhc0ttqmy.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).