unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: rm@fabula.de
Cc: rm@fabula.de, Marius Vollmer <mvo@zagadka.ping.de>,
	Neil Jerram <neil@ossau.uklinux.net>,
	guile-devel@gnu.org
Subject: Re: Release status 1.6.1 (2002-05-16)
Date: Tue, 28 May 2002 12:22:22 +0200	[thread overview]
Message-ID: <20020528102222.GB29680@www> (raw)
In-Reply-To: <873cwczy6g.fsf@raven.i.defaultvalue.org>

On Mon, May 27, 2002 at 11:36:07PM -0500, Rob Browning wrote:
> [...]

Thanks for the clarification.
 
> So the question is, what *is* the right thing to do?  The FSF
> "standards" info pages have a little relevant info, but nothing
> definitive:
> 
>    The `README' file should also refer to the file which contains the
>    copying conditions.  The GNU GPL, if used, should be in a file
>    called `COPYING'.  If the GNU LGPL is used, it should be in a file
>    called `COPYING.LIB'.

Ah, licences with namespaces ;-) So why not COPYING.GUILE and GPL?
I have to admit that i didn't see the amount of work required to rename
the files (never rename base classes).

> So I've filed a bug against the GNU standards package.  Let's see what
> they say...

Delegate ...

 Thanks, Ralf

> 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

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-05-28 10:22 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
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 [this message]
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=20020528102222.GB29680@www \
    --to=rm@fabula.de \
    --cc=guile-devel@gnu.org \
    --cc=mvo@zagadka.ping.de \
    --cc=neil@ossau.uklinux.net \
    /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).