From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: Guile web page docs
Date: Mon, 26 Oct 2009 07:55:09 +0000 [thread overview]
Message-ID: <87ocnupp2a.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87ws2jpak3.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 25 Oct 2009 19:56:12 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> Hi,
>
> Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> Yes, but amusingly this copy of the manual is only linked from the
>> "support for many SRFIs" link on
>> http://www.gnu.org/software/guile/guile.html, and from inside Daniel's
>> tutorial.
>
> And from http://gnu.org/manual/ .
Ah, thanks.
> Indeed. I think I’ve always been updating the one at guile/manual,
> since it’s the usual way to place GNU manuals, but I must have forgotten
> to check the links under guile/. I’d be in favor or removing ‘docs-1.8’
> and keeping just ‘manual’. What do you think?
Agreed, and I've done that now.
>>> (BTW, Gnulib has a new script to automate updates to
>>> www.gnu.org/software/PROJECT/manual.)
>>
>> Right; I assume you mean gendocs.sh.
>
> I was thinking about the ‘gnu-web-doc-update’ module.
I'll take a look, thanks.
>> Do you have strong views on whether we should use current Git or the
>> latest pre-release? I don't think it matters much, and current Git is
>> marginally easier.
>
> Either way is fine with me.
Cool, I'll sort out a 1.9/2.0 set of docs later.
Neil
next prev parent reply other threads:[~2009-10-26 7:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 20:47 Guile web page docs Neil Jerram
2009-10-21 21:25 ` Ludovic Courtès
2009-10-23 22:25 ` Neil Jerram
2009-10-25 18:56 ` Ludovic Courtès
2009-10-26 7:55 ` Neil Jerram [this message]
2009-10-27 22:46 ` Neil Jerram
2009-10-28 22:53 ` Neil Jerram
2009-10-28 23:20 ` Ludovic Courtès
2009-10-29 8:26 ` Andy Wingo
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ocnupp2a.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=ludo@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).