unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Sebastian Tennant <sebyte@smolny.plus.com>
Cc: guile-user@gnu.org
Subject: Re: ttn-pers-scheme & ttn-do
Date: Sun, 25 May 2008 20:12:47 +0200	[thread overview]
Message-ID: <87abieqmlc.fsf@ambire.localdomain> (raw)
In-Reply-To: <87wsn33u9j.fsf@moley.moleskin.org> (Sebastian Tennant's message of "Sat, 12 Apr 2008 19:36:24 +0300")

() Sebastian Tennant <sebyte@smolny.plus.com>
() Sat, 12 Apr 2008 19:36:24 +0300

   > The special exception can be seen in some Guile
   > releases in the top-level README:
   >
   > | The exception is that, if you link the GUILE library with
   > | other files to produce an executable, this does not by
   > | itself cause the resulting executable to be covered by the
   > | GNU General Public License.  Your use of that executable is
   > | in no way restricted on account of linking the GUILE
   > | library code into it.

   Presumably this is/was to encourage use of Guile
   across the board (i.e., in non-free environments too)?

Yes, i believe so.

   Thanks for taking the time to write this.  I can't say exactly
   _why_ it's nice to know how the situation came about, but it
   is, nevertheless.

You're welcome.  It can be both pleasant and unpleasant to
re-re-re-reverbrate.  That's the nature of troughs and crests.

thi




      reply	other threads:[~2008-05-25 18:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18 20:20 ttn-pers-scheme & ttn-do Sebastian Tennant
2008-03-19  7:35 ` Thien-Thi Nguyen
2008-03-19 11:08   ` Sebastian Tennant
2008-04-03 11:28     ` Thien-Thi Nguyen
2008-04-03 11:47       ` Thien-Thi Nguyen
2008-04-12 16:36       ` Sebastian Tennant
2008-05-25 18:12         ` Thien-Thi Nguyen [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=87abieqmlc.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --cc=guile-user@gnu.org \
    --cc=sebyte@smolny.plus.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).