Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: CVS update of gnus/texi (ChangeLog auth.texi)
Date: Mon, 13 Apr 2009 10:53:07 -0500	[thread overview]
Message-ID: <86bpr0tusc.fsf@lifelogs.com> (raw)
In-Reply-To: <b4mhc0ttqmy.fsf@jpl.org>

On Mon, 13 Apr 2009 08:10:29 +0900 Katsumi Yamaoka <yamaoka@jpl.org> wrote: 

>>>>>> Reiner Steib wrote:
>> There's on line that needs to be different:

>> In Gnus:    @setfilename auth.info

>> In Emacs:   @setfilename ../../info/auth

KY> Ok.  I've synch'd up the No Gnus version with Emacs except for
KY> that line.  Now the Info file name is "auth", not "auth.info",
KY> that follows the No Gnus convention.

Thanks!  I will be revising the content of auth.texi soon, and I
appreciate the syntax corrections very much.

Ted




      reply	other threads:[~2009-04-13 15:53 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
2009-04-13 15:53       ` Ted Zlatanov [this message]

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=86bpr0tusc.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).