From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Release status 1.6.1 (2002-05-16)
Date: Wed, 22 May 2002 09:23:26 -0500 [thread overview]
Message-ID: <87r8k41ctd.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87r8k41h0j.fsf@zagadka.ping.de> (Marius Vollmer's message of "22 May 2002 14:52:44 +0200")
Marius Vollmer <mvo@zagadka.ping.de> writes:
> I'd say that this is not release critical as it does not affect the
> release.
I was leaning that way as well.
>> (4) bugs/COPYING-is-wrong [rlb]
>>
>> Umm, COPYING is now the GPL in CVS. Perhaps I should fix that :>
>
> Has this been resolved with our private mails? For everybody to see:
[...]
> I'm hesitant to change COPYING as it is a 'standard' file with
> identical contents in a lot of packages.
Hmm. I had tended to think of COPYING as the 'standard' place (when
it existed) to look to see what license the authors wanted for the
whole project. So I was just worried that people may look there first
and continue under the assumption that Guile is only under the GPL.
As long as it's clear which part of COPYING is the GPL, then all the
text in the source files should be OK since they just say that the GPL
is in COPYING, which it is (along with the disclaimer, which they may
have already seen if coming from a source file).
Anyway, not a big deal either way -- since the README mentions the
exception, I guess most people are likely to read that even before
checking COPYING. I'm now OK with closing this bug if you like.
Thanks
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-05-22 14:23 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 [this message]
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
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=87r8k41ctd.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.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).