From: rm@fabula.de
Cc: Rob Browning <rlb@defaultvalue.org>,
Marius Vollmer <mvo@zagadka.ping.de>,
guile-devel@gnu.org
Subject: Re: Release status 1.6.1 (2002-05-16)
Date: Sun, 26 May 2002 18:59:39 +0200 [thread overview]
Message-ID: <20020526165939.GA27611@www> (raw)
In-Reply-To: <m3n0uorzcr.fsf@laruns.ossau.uklinux.net>
On Sat, May 25, 2002 at 05:01:08PM +0100, Neil Jerram wrote:
> >>>>> "Rob" == Rob Browning <rlb@defaultvalue.org> writes:
>
> Rob> Anyway, not a big deal either way -- since the README mentions the
> Rob> exception, I guess most people are likely to read that even before
> Rob> checking COPYING. I'm now OK with closing this bug if you like.
>
> Just an idea: we could leave COPYING as is, and add COPYING-GUILE to
> explain the exception and refer to COPYING. Then most people going to
> look for COPYING would notice COPYING-GUILE as well. The text for
> COPYING-GUILE can be the same as what is currently in README.
Hmm, just in my own experience, COPYING is _the_ file i look at to
determine the licence of the software. If i find the GPL i would assume
that the whole software _is_ GLPed (which GUILE is not). If putting Guile's
license under the name COPYING feels strange, why not just name it LICENCE
and name the GPL 'GPL-LICENCE'? Just naming the GPL copying out of tradition
even so it's not the legal copying restriction sounds rather odd to me - i think
the whole licence/copyright issue is messy enough, let's try to keep thinks as
'waterproof' as possible (refering to the text of the README file to establish
a legaly binding licence agreement sounds rather risky :-)
Ralf Mattes
> Neil
>
>
> _______________________________________________
> Guile-devel mailing list
> Guile-devel@gnu.org
> http://mail.gnu.org/mailman/listinfo/guile-devel
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-05-26 16:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-16 23:12 Release status 1.6.1 (2002-05-16) Rob Browning
2002-05-22 12:52 ` Marius Vollmer
2002-05-22 14:23 ` Rob Browning
2002-05-22 14:52 ` Marius Vollmer
2002-05-22 15:12 ` Marius Vollmer
2002-05-25 16:01 ` Neil Jerram
2002-05-25 17:12 ` Dale P. Smith
2002-05-25 23:04 ` Rob Browning
2002-05-27 20:37 ` Marius Vollmer
2002-05-26 16:59 ` rm [this message]
2002-05-26 17:54 ` Jeff Read
2002-05-27 20:44 ` Marius Vollmer
2002-05-27 21:38 ` rm
2002-05-28 4:36 ` Rob Browning
2002-05-28 10:22 ` rm
2002-05-28 16:09 ` Rob Browning
2002-05-28 17:45 ` Marius Vollmer
2002-05-28 17:55 ` Marius Vollmer
2002-05-28 18:11 ` Rob Browning
2002-05-28 19:27 ` Marius Vollmer
2002-05-30 16:26 ` Rob Browning
2002-05-30 17:45 ` Marius Vollmer
2002-05-30 18:05 ` rm
2002-05-30 19:21 ` Rob Browning
2002-05-30 19:33 ` Marius Vollmer
2002-05-28 17:53 ` Marius Vollmer
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=20020526165939.GA27611@www \
--to=rm@fabula.de \
--cc=guile-devel@gnu.org \
--cc=mvo@zagadka.ping.de \
--cc=rlb@defaultvalue.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).