unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Leo <sdl.web@gmail.com>
Cc: 10759@debbugs.gnu.org, Ding Mailing List <ding@gnus.org>
Subject: bug#10759: 23.4; Move url-future-test to test/
Date: Wed, 15 Feb 2012 08:41:38 -0500	[thread overview]
Message-ID: <87k43o2oz1.fsf__44778.4924218014$1329314130$gmane$org@lifelogs.com> (raw)
In-Reply-To: <87pqdh44e8.fsf__31901.4797722504$1329246706$gmane$org@lifelogs.com> (Ted Zlatanov's message of "Tue, 14 Feb 2012 14:10:55 -0500")

On Tue, 14 Feb 2012 14:10:55 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> On Wed, 15 Feb 2012 01:37:22 +0800 Leo <sdl.web@gmail.com> wrote: 
L> On 2012-02-14 21:20 +0800, Ted Zlatanov wrote:
>>> Yes, for Gnus it's better to keep them as they are.  Perhaps if Gnus had
>>> its own test directory...

L> On 2012-02-14 22:34 +0800, Lars Ingebrigtsen wrote:
>>> I just noticed the other day that there's a "tests" directory in git
>>> Gnus.  :-)

L> I think we have what is needed to separate those tests and put them in
L> the dedicated folders. What do you think?

TZ> Done, correctly I hope.

TZ> Ding list: all the registry.el and gnus-registry.el ERT tests are moved
TZ> to tests/gnustest-registry.el

TZ> Any other tests I should move?

I think we're OK now; can I close this bug?

Ted





  reply	other threads:[~2012-02-15 13:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08  5:40 bug#10759: 23.4; Move url-future-test to test/ Leo
2012-02-13 18:47 ` Ted Zlatanov
2012-02-14  1:23   ` Leo
2012-02-14  1:50     ` Glenn Morris
2012-02-14  2:40       ` Leo
2012-02-14 13:20         ` Ted Zlatanov
2012-02-14 14:34           ` Lars Ingebrigtsen
2012-02-14 17:37           ` Leo
2012-02-14 19:10             ` Ted Zlatanov
2012-02-15 13:41               ` Ted Zlatanov [this message]
2012-02-15 14:27                 ` Leo

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='87k43o2oz1.fsf__44778.4924218014$1329314130$gmane$org@lifelogs.com' \
    --to=tzz@lifelogs.com \
    --cc=10759@debbugs.gnu.org \
    --cc=ding@gnus.org \
    --cc=sdl.web@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).