From: David Engster <deng@randomsample.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs-Devel devel <emacs-devel@gnu.org>,
PJ Weisberg <pjweisberg@gmail.com>
Subject: Re: Tests and copyright
Date: Thu, 15 Aug 2013 18:10:37 +0200 [thread overview]
Message-ID: <87r4dvorya.fsf@engster.org> (raw)
In-Reply-To: <jwv1u5vivkl.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 14 Aug 2013 21:50:21 -0400")
Stefan Monnier writes:
> My opinion is that it is not necessary to get copyright assignments for
> the test cases themselves (e.g. the files in emacs/test/indent, or the
> compile-tests--test-regexps-data var in test/automated/compile-tests.el).
>
> That still leaves open the question for the code written to actually run
> the tests (e.g. the functions compile--test-error-line and
> compile-test-error-regexps in that same
> test/automated/compile-tests.el). To the extent that this code is
> likely to have parts that can be reused between different sets of tests
> for different packages, I tend to think that it falls in the camp of
> "it's just code like any other".
>
>> Anyway, I was just hoping that I wouldn't have to wade through years of
>> log history, as if porting test code wasn't boring enough already.
>
> Is the above rule "lax enough" to significantly lighten your workload?
No, I'm afraid not; it's really about the code that runs the test.
So I guess I'll just have to look through the history; I guess/hope that
Eric has written almost all of it anyway. The main problem is that we
weren't very careful with the tests when migrating to bzr, so I'll have
to checkout the old CVS repository (and the crowd goes "Eww!", but I'm
sure they just marvel at Lars' shiny new browser).
-David
next prev parent reply other threads:[~2013-08-15 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 19:49 Tests and copyright David Engster
2013-08-14 16:04 ` PJ Weisberg
2013-08-14 21:33 ` David Engster
2013-08-15 1:50 ` Stefan Monnier
2013-08-15 16:10 ` David Engster [this message]
2013-08-15 16:48 ` Stefan Monnier
2013-08-16 0:54 ` Eric M. Ludlam
2013-08-16 15:35 ` David Engster
2013-08-19 21:06 ` David Engster
2013-08-15 4:16 ` Stephen J. Turnbull
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=87r4dvorya.fsf@engster.org \
--to=deng@randomsample.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=pjweisberg@gmail.com \
/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).