From: Andy Wingo <wingo@pobox.com>
To: b3timmons@speedymail.org
Cc: guile-user@gnu.org
Subject: Re: Any advice about improving the docs?
Date: Mon, 09 Jan 2012 19:57:49 +0100 [thread overview]
Message-ID: <87mx9w66vm.fsf@pobox.com> (raw)
In-Reply-To: <87ipn1coos.fsf@goof.bjgalaxy> (42toes@gmail.com's message of "Thu, 03 Nov 2011 09:37:07 -0400")
On Thu 03 Nov 2011 14:37, 42toes@gmail.com writes:
> I seek advice on making the Guile manual and docstrings clearer and more
> consistent, two qualities that I think novices especially appreciate.
We are still very much interested in your contributions, especially now
that the assignment forms are in :-)
We will be releasing a 2.0.4 soonish, perhaps within a week, and so now
is a perfect time to send a series of small, easy-to-apply,
git-format-patch produced attachments to the list :-)
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2012-01-09 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 13:37 Any advice about improving the docs? 42toes
2011-11-04 16:44 ` Ludovic Courtès
2012-01-09 18:57 ` Andy Wingo [this message]
2012-01-10 13:12 ` Bake Timmons
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=87mx9w66vm.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=b3timmons@speedymail.org \
--cc=guile-user@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).