unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Ian Price <ianprice90@googlemail.com>
Cc: bug-guile@gnu.org
Subject: Re: (@ (rnrs base) log) optional second argument
Date: Mon, 11 Apr 2011 17:57:59 +0200	[thread overview]
Message-ID: <m37hb0n5ko.fsf@unquote.localdomain> (raw)
In-Reply-To: <BANLkTi=90FXeuOb3aVUqHbTPqZkYfai6Pg@mail.gmail.com> (Ian Price's message of "Wed, 6 Apr 2011 02:11:23 +0100")

Hi Ian,

On Wed 06 Apr 2011 03:11, Ian Price <ianprice90@googlemail.com> writes:

> Guile does not implement the optional second argument for log. I have
> attached a simple patch that implements it using the formula you learn
> in high school.

Thanks, applied.

We're brushing the point at which you should assign copyright to the
FSF.  Are you OK with that?  Please let me know and I'll kick off the
process.

Thanks,

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2011-04-11 15:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06  1:11 (@ (rnrs base) log) optional second argument Ian Price
2011-04-11 15:57 ` Andy Wingo [this message]
2011-04-11 16:52   ` 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=m37hb0n5ko.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=bug-guile@gnu.org \
    --cc=ianprice90@googlemail.com \
    /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).