unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Improved exactness handling for complex number parsing
Date: Thu, 10 Feb 2011 16:08:51 -0500	[thread overview]
Message-ID: <877hd7wqak.fsf@yeeloong.netris.org> (raw)
In-Reply-To: <87fws2plh5.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 05 Feb 2011 16:08:54 +0100")

ludo@gnu.org (Ludovic Courtès) writes:
> One nitpick: it would be nice if (part of) the documentation that’s in
> the commit logs were in the source files, so one sees it when reading
> the corresponding code.

Excellent suggestion.  I've just submitted a patch to do this.

   Thanks!
     Mark



      reply	other threads:[~2011-02-10 21:08 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
2011-02-05 15:08       ` Ludovic Courtès
2011-02-10 21:08         ` Mark H Weaver [this message]

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=877hd7wqak.fsf@yeeloong.netris.org \
    --to=mhw@netris.org \
    --cc=guile-devel@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).