unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Quasisyntax broken?
Date: Thu, 20 Aug 2009 23:19:48 +0200	[thread overview]
Message-ID: <87ljleji8b.fsf@gnu.org> (raw)
In-Reply-To: 87ljmcsb6r.fsf@delenn.lan

Hey!

The outcome of a discussion with RMS and Karl Berry is that we can
include this code under its current license in Guile.  It would be
preferable to store it in a separate file, though, with the full license
text in the header.

Could you prepare an updated patch based on this?

Thanks,
Ludo'.





      parent reply	other threads:[~2009-08-20 21:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-03  0:04 Quasisyntax broken? Andreas Rottmann
2009-07-23 21:31 ` Andy Wingo
2009-07-23 22:35   ` Andreas Rottmann
2009-07-23 22:48     ` Andy Wingo
2009-07-25 21:30       ` Andreas Rottmann
2009-07-26 13:15         ` Ludovic Courtès
2009-07-26 16:30         ` Andy Wingo
2009-07-26 22:06           ` Ludovic Courtès
2009-07-27 22:51             ` Neil Jerram
2009-08-20 21:19         ` Ludovic Courtès [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=87ljleji8b.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@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).