From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Christian Ohler <ohler+emacs@fastmail.net>
Cc: Chong Yidong <cyd@stupidchicken.com>,
Sebastian Rose <sebastian_rose@gmx.de>,
Lennart Borgman <lennart.borgman@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel Mailinglist <emacs-devel@gnu.org>
Subject: Re: testing framework and package.el
Date: Wed, 13 Oct 2010 23:19:05 +0900 [thread overview]
Message-ID: <87pqve2n1i.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <4CB58359.3060001@fastmail.net>
Christian Ohler writes:
> IIUC, this design requires developers who want to add features and write
> tests for them to check out two different bzr branches and submit two
> different patches.
Currently, yes. With nested branches, the checkout will be implicit.
> Isn't that a rather high bar that will be inconvenient for
> developers and discourage them from writing tests?
In my experience, people who actually write tests (unless there's a
firm requirement that tests be submitted before committing) are hard
to discourage. The only job programmers like less than writing tests
is writing docs. :-)
The real problem is getting those tests backported.
> As an alternative that avoids this problem, we could maintain the tests
> in Emacs trunk, but our makefiles could have a test_src variable that
> defaults to tests, and that we can set to ../trunk/tests when running
> tests in the emacs-23 directory in Stephen's layout.
Which still requires serious developers to have multiple checkouts.
next prev parent reply other threads:[~2010-10-13 14:19 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 15:18 testing framework and package.el Sebastian Rose
2010-09-27 22:57 ` Stefan Monnier
2010-09-27 23:42 ` Sebastian Rose
2010-09-27 23:55 ` Sebastian Rose
2010-10-01 13:01 ` Christian Ohler
2010-10-02 3:53 ` Sebastian Rose
2010-10-03 10:51 ` Christian Ohler
2010-10-03 20:52 ` Sebastian Rose
2010-10-04 15:36 ` Christian Ohler
2010-10-04 16:48 ` Chong Yidong
2010-10-05 1:17 ` Christian Ohler
2010-10-05 1:38 ` Lennart Borgman
2010-10-05 1:50 ` Sebastian Rose
2010-10-05 3:31 ` Christian Ohler
2010-10-05 4:39 ` Stephen J. Turnbull
2010-10-05 16:43 ` Eric Schulte
2010-10-05 23:18 ` Stefan Monnier
2010-10-11 9:26 ` Christian Ohler
2010-10-12 3:02 ` Stephen J. Turnbull
2010-10-12 9:41 ` Lennart Borgman
2010-10-12 13:39 ` Stephen J. Turnbull
2010-10-12 16:28 ` Lennart Borgman
2010-10-12 17:37 ` Stephen J. Turnbull
2010-10-12 17:54 ` Lennart Borgman
2010-10-13 0:36 ` Stefan Monnier
2010-10-13 9:03 ` Stephen J. Turnbull
2010-10-13 10:00 ` Christian Ohler
2010-10-13 14:19 ` Stephen J. Turnbull [this message]
2010-10-17 6:37 ` Christian Ohler
2010-10-17 14:54 ` Stefan Monnier
2010-10-18 6:55 ` Stephen J. Turnbull
2010-10-12 14:36 ` Christian Ohler
2010-10-12 17:41 ` Stephen J. Turnbull
2010-10-13 10:00 ` Christian Ohler
2010-10-13 14:13 ` Stephen J. Turnbull
2010-10-17 6:37 ` Christian Ohler
2010-10-12 14:19 ` Christian Ohler
2010-10-12 17:58 ` Stephen J. Turnbull
2010-10-12 18:13 ` Lennart Borgman
2010-10-13 10:00 ` Christian Ohler
2010-10-04 17:22 ` Eric Schulte
2010-10-05 0:01 ` Sebastian Rose
2010-10-04 13:02 ` Masatake YAMATO
2010-10-05 3:29 ` Christian Ohler
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=87pqve2n1i.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=ohler+emacs@fastmail.net \
--cc=sebastian_rose@gmx.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 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).