unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] Portability fix for new log and log10
Date: Tue, 22 Feb 2011 20:29:01 +0100	[thread overview]
Message-ID: <m3ei6zx402.fsf@unquote.localdomain> (raw)
In-Reply-To: <87sjvl194s.fsf@netris.org> (Mark H. Weaver's message of "Fri, 18 Feb 2011 13:37:55 -0500")

On Fri 18 Feb 2011 19:37, Mark H Weaver <mhw@netris.org> writes:

> From 873dfab119592658adce812a0fea0d6a688a3637 Mon Sep 17 00:00:00 2001
> From: Mark H Weaver <mhw@netris.org>
> Date: Tue, 15 Feb 2011 19:29:41 -0500
> Subject: [PATCH] Portability fix for new log and log10
>
> * libguile/numbers.c: Define M_LN2 if it's not already defined.
>   Fix error in comment.

Now that you have the commit bit, please go ahead and push this one.
Thanks :)

Andy
-- 
http://wingolog.org/



           reply	other threads:[~2011-02-22 19:29 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <87sjvl194s.fsf@netris.org>]

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=m3ei6zx402.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).