From: Andy Wingo <wingo@pobox.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] Improved exactness handling for complex number parsing
Date: Thu, 03 Feb 2011 10:51:47 +0100 [thread overview]
Message-ID: <m3mxmdsax8.fsf@unquote.localdomain> (raw)
In-Reply-To: <877hdhtr7v.fsf_-_@yeeloong.netris.org> (Mark H. Weaver's message of "Thu, 03 Feb 2011 04:14:28 -0500")
On Thu 03 Feb 2011 10:14, Mark H Weaver <mhw@netris.org> writes:
> This patch implements the ideas outlined in my response to Mike Gran's
> recent post entitled "Effects of updated number fixes on parsing".
Applied, and thanks again for the high quality of these patches, their
commit logs, and the news entries and documentation updates! A pleasure
working with you :)
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-02-03 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 0:47 Effects of updated number fixes on parsing Mike Gran
2011-02-03 4:01 ` Mark H Weaver
2011-02-03 9:14 ` [PATCH] Improved exactness handling for complex number parsing Mark H Weaver
2011-02-03 9:51 ` Andy Wingo [this message]
2011-02-05 15:08 ` Ludovic Courtès
2011-02-10 21:08 ` Mark H Weaver
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=m3mxmdsax8.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.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).