Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Re: no gnus registry new dependency on ert?
Date: Wed, 06 Apr 2011 10:51:45 -0500	[thread overview]
Message-ID: <87oc4jpecu.fsf@lifelogs.com> (raw)
In-Reply-To: <m262qrzajt.fsf@randomsample.de>

On Wed, 06 Apr 2011 17:03:50 +0200 David Engster <deng@randomsample.de> wrote: 

DE> Addendum: Maybe the "real" solution is to have the tests in a separate
DE> file, so that a (require 'registry) won't instantiate the ERT tests. I
DE> can see why having the tests in the file itself can be convenient, but
DE> usually, test-suites are separated from the actual code? Anyway, I don't
DE> really have a strong opinion on this.

I considered that approach but I think it's cleaner and easier to do it
in one file, if there are no technical reasons against it.

Ted




  reply	other threads:[~2011-04-06 15:51 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06  4:28 Eric Abrahamsen
2011-04-06 10:03 ` Ted Zlatanov
2011-04-06 10:10   ` David Engster
2011-04-06 10:54     ` Ted Zlatanov
2011-04-06 13:10       ` Ted Zlatanov
2011-04-06 13:28         ` David Engster
2011-04-06 14:26           ` Ted Zlatanov
2011-04-06 14:57             ` David Engster
2011-04-06 15:00               ` Ted Zlatanov
2011-04-06 15:03               ` David Engster
2011-04-06 15:51                 ` Ted Zlatanov [this message]
2011-04-06 13:15 ` Gnus automatic builds (was: no gnus registry new dependency on ert?) Ted Zlatanov
2011-04-06 13:31   ` Gnus automatic builds David Engster
2011-04-06 16:14     ` David Engster
2011-04-06 16:30       ` Ted Zlatanov
2011-04-06 18:10         ` David Engster
2011-04-06 18:57           ` Ted Zlatanov
2011-04-07 19:21             ` David Engster
2011-04-07 19:51               ` Ted Zlatanov
2011-04-07 20:02                 ` David Engster
2011-04-07 21:19                   ` Ted Zlatanov
2011-04-12 16:08               ` Lars Magne Ingebrigtsen
2011-04-12 16:29                 ` David Engster
2011-04-12 16:36                   ` Lars Magne Ingebrigtsen
2011-04-12 18:33                     ` Jason L Tibbitts III
2011-04-12 18:41                       ` Lars Magne Ingebrigtsen
2011-04-12 19:35                         ` Jason L Tibbitts III
2011-04-12 19:46                           ` David Engster
2011-04-12 19:51                             ` Jason L Tibbitts III
2011-04-16  8:22                               ` David Engster
2011-04-16 15:19                                 ` Ted Zlatanov
2011-04-20 18:50                                   ` David Engster
2011-04-20 20:58                                     ` Ted Zlatanov
2011-04-22 11:27                                     ` Adam Sjøgren
2011-04-22 21:21                                       ` David Engster
2011-04-25  9:05                                         ` Adam Sjøgren
2011-04-12 20:00                           ` Lars Magne Ingebrigtsen
2011-04-20 20:59                         ` David Engster
2011-04-20 21:03                           ` Ted Zlatanov
2011-04-20 21:31                             ` Jason L Tibbitts III
2011-04-21  7:33                               ` David Engster
2011-04-25 12:28                             ` Ted Zlatanov
2011-04-06 20:26       ` David Engster
2011-04-07 19:30         ` David Engster

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=87oc4jpecu.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    /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 NNTP newsgroup(s).