unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: "Lennart Borgman \(gmail\)" <lennart.borgman@gmail.com>
Cc: rms@gnu.org, "Stephen J. Turnbull" <turnbull@sk.tsukuba.ac.jp>,
	emacs-devel@gnu.org
Subject: Re: Need for a Emacs regression test suite
Date: Sun, 09 Sep 2007 12:13:57 +0200	[thread overview]
Message-ID: <85ir6kqh7e.fsf@lola.goethe.zz> (raw)
In-Reply-To: <46E3C0C9.30409@gmail.com> (Lennart Borgman's message of "Sun\, 09 Sep 2007 11\:45\:45 +0200")

"Lennart Borgman (gmail)" <lennart.borgman@gmail.com> writes:

> David Kastrup wrote:
>> I would suggest that you are careful not to invest too much
>> Emacs-specific work that might be lost ultimately due to legal
>> reasons, though this warning might appear somewhat premature at the
>> moment.
>
> Could not the testing framework be used by developers even if there
> are some legal problems with it?

Using third-party tools should not constitute a problem when they are
licensed under appropriate terms.  But in this case the main modus of
operandi means extending the test case base, and that implies an
investment of work.  So there is some desire to not make this sort of
work entangled with code where it is not clear that we will always be
able to use it, or distribute it.

The GNU project has always tried to keep core components of the GNU
system copyrighted by the FSF.  If a testing suite becomes an integral
part of developing Emacs, something that we rely on, it would be
desirable to have this the case here as well.

That does not mean that it would be impossible to work with it
otherwise, but if we have a chance of ensuring this, it would be
better to do so.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2007-09-09 10:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-08 17:51 Need for a Emacs regression test suite dhruva
2007-09-08 18:19 ` Lennart Borgman (gmail)
2007-09-08 20:22 ` Stephen J. Turnbull
     [not found] ` <E1IUCJD-0000Zk-BP@fencepost.gnu.org>
     [not found]   ` <e3f230850709082119s92e13abi65f674b3b0c9b171@mail.gmail.com>
2007-09-09  8:05     ` David Kastrup
2007-09-09  9:45       ` Lennart Borgman (gmail)
2007-09-09 10:13         ` David Kastrup [this message]
2007-09-09 20:06     ` Richard Stallman
2007-09-10 19:08       ` Stephen J. Turnbull
2007-09-10 19:12         ` Davis Herring
2007-09-11  5:00         ` Mathias Dahl
2007-09-11  6:08           ` Stephen J. Turnbull
2007-09-11 20:30         ` Richard Stallman
2007-09-12  4:44           ` Stephen J. Turnbull
2007-09-13 16:29             ` Richard Stallman
2007-09-10 20:12     ` Stephen J. Turnbull
2007-09-11  3:50       ` dhruva
2007-09-11 14:43         ` Stephen J. Turnbull
2007-09-11 19:33         ` Eli Zaretskii

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/emacs/

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

  git send-email \
    --in-reply-to=85ir6kqh7e.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman@gmail.com \
    --cc=rms@gnu.org \
    --cc=turnbull@sk.tsukuba.ac.jp \
    /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 public inbox

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

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).