From: Ian Price <ianprice90@googlemail.com>
To: David Kastrup <dak@gnu.org>
Cc: 15586@debbugs.gnu.org
Subject: bug#15586: [PATCH] Documentation fix for unfold-right in srfi-1
Date: Sat, 19 Oct 2013 22:58:45 +0100 [thread overview]
Message-ID: <87hacc29c7.fsf@Kagami.home> (raw)
In-Reply-To: <1381479562-30860-1-git-send-email-dak@gnu.org>
Funny thing is, I was just about to fire off an email about why this fix
was wrong, and just before posting realised this was a patch for
unfold-right, not unfold.
I was unsure of whether to go with the srfi wording or your wording, but
yours is a little better so I kept it.
Cheers
--
Ian Price -- shift-reset.com
"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"
next prev parent reply other threads:[~2013-10-19 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 8:19 bug#15586: [PATCH] Documentation fix for unfold-right in srfi-1 David Kastrup
2013-10-18 12:38 ` bug#15586: Ping? David Kastrup
2013-10-19 21:58 ` Ian Price [this message]
2013-10-19 22:19 ` bug#15586: [PATCH] Documentation fix for unfold-right in srfi-1 Ian Price
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=87hacc29c7.fsf@Kagami.home \
--to=ianprice90@googlemail.com \
--cc=15586@debbugs.gnu.org \
--cc=dak@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).