From: Daniel Llorens <daniel.llorens@bluewin.ch>
To: Andy Wingo <wingo@pobox.com>
Cc: bug-guile@gnu.org, Mark H Weaver <mhw@netris.org>
Subject: Re: multiple values bug in head / call-with-input-file
Date: Mon, 2 May 2011 23:20:18 +0200 [thread overview]
Message-ID: <9B6FC313-3F93-4C4D-A171-0DADE6B6912E@bluewin.ch> (raw)
In-Reply-To: <m3d3k0u8j3.fsf@unquote.localdomain>
On May 2, 2011, at 22:55, Andy Wingo wrote:
> We are brushing the copyright assignment limits here; I'll apply this,
> but if you are interested in sending further patches to Guile, would you
> be OK with assigning copyright to the FSF? Please let me know, and I'll
> send you details in a private mail.
You are too kind; I just copied Mark's fix. Anyway, sure, I'll sign.
> Thanks for the patch, and happy hacking :)
Thanks to you!
Regards,
Daniel
prev parent reply other threads:[~2011-05-02 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 13:23 multiple values bug in head / call-with-input-file Daniel Llorens
2011-05-02 17:46 ` Mark H Weaver
2011-05-02 19:09 ` Daniel Llorens
2011-05-02 20:55 ` Andy Wingo
2011-05-02 21:20 ` Daniel Llorens [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=9B6FC313-3F93-4C4D-A171-0DADE6B6912E@bluewin.ch \
--to=daniel.llorens@bluewin.ch \
--cc=bug-guile@gnu.org \
--cc=mhw@netris.org \
--cc=wingo@pobox.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).