all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Jan Moringen <jan.moringen@uni-bielefeld.de>
Cc: emacs-devel@gnu.org
Subject: Re: Potential copyright problem in EIEIO improvement
Date: Sun, 03 Jan 2010 23:09:40 -0500	[thread overview]
Message-ID: <E1NReGC-0007oX-8t@fencepost.gnu.org> (raw)
In-Reply-To: <3504_1262544732_ZZg0O73~B6ki9.00_1262544727.3761.1636.camel@localhost.localdomain> (message from Jan Moringen on Sun, 03 Jan 2010 19:52:07 +0100)

    The following piece of code is from the paper "A Monotonic Superclass
    Linearization for Dylan". It is labeled "Appendix A: Implementation of
    the Dylan Linearization" there. This code implements the Dylan
    linearization *without* the improvement presented in the paper.

That is 50 lines, which is far more than enough that we would
normally want papers.

Can we make an exception for this case?  Maybe.  I will ask a lawyer.

Which GPL versions does Open Dylan's license allow?




  reply	other threads:[~2010-01-04  4:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-30  2:49 Potential copyright problem in EIEIO improvement Jan Moringen
2009-12-30  5:42 ` Eli Zaretskii
2009-12-31  3:16   ` Jan Moringen
2009-12-31  1:45 ` Richard Stallman
2009-12-31  3:25   ` Jan Moringen
2010-01-01  2:55     ` Richard Stallman
2010-01-01 18:52       ` Jan Moringen
2010-01-02 15:45         ` Richard Stallman
2010-01-03 18:52           ` Jan Moringen
2010-01-04  4:09             ` Richard Stallman [this message]
2010-01-04  5:37               ` Jan Moringen
2010-01-04 16:23                 ` Richard Stallman
2010-01-05  4:23                   ` Jan Moringen
2010-01-05 20:45                     ` Richard Stallman
2010-01-06  8:11                       ` David Kastrup
2010-01-30 21:32             ` Richard Stallman
2010-02-01  3:02               ` Jan Moringen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1NReGC-0007oX-8t@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jan.moringen@uni-bielefeld.de \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.