public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Hans Ronne <hronne@comhem.se>
Cc: xconq7@sources.redhat.com
Subject: Re: Xconq on-line manual updated
Date: Fri, 21 May 2004 00:17:00 -0000	[thread overview]
Message-ID: <1085098565.1485.182.camel@localhost.localdomain> (raw)
In-Reply-To: <l03130302bcd2cef8dda7@[212.181.162.155]>

On Thu, 2004-05-20 at 15:11, Hans Ronne wrote:
> the Xconq on-line manual has been updated from the texi sources. See:
> 
> http://sources.redhat.com/xconq/manual/xconq_1.html
> 
> http://sources.redhat.com/xconq/manual/xcdesign_1.html
> 
> http://sources.redhat.com/xconq/manual/hacking_1.html

Just for the record: I have been updating the relevant on-line manuals
whenever I have made changes to the TexInfo sources. The most recent
update that I made was on 2004/05/13 to the Game Design Manual
(xcdesign_*.html).

Eric

  reply	other threads:[~2004-05-21  0:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-20 21:13 Hans Ronne
2004-05-21  0:17 ` Eric McDonald [this message]
2004-05-21  1:14   ` Hans Ronne

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=1085098565.1485.182.camel@localhost.localdomain \
    --to=mcdonald@phy.cmich.edu \
    --cc=hronne@comhem.se \
    --cc=xconq7@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).