perl.qa archive

370 archived articles, newest first (page 4 of 4). Latest articles →

Re: TPF Devel::Cover grant report May 2013
Sun, 01 Sep 2013 01:34:03 +0200
[email protected] ("Christian Walde") • #13492
TPF Devel::Cover grant report August 2013
Sun, 1 Sep 2013 01:02:48 +0200
[email protected] (Paul Johnson) • #13491
TPF Devel::Cover grant report July 2013
Sun, 1 Sep 2013 01:01:09 +0200
[email protected] (Paul Johnson) • #13490
TPF Devel::Cover grant report June 2013
Sun, 1 Sep 2013 00:59:11 +0200
[email protected] (Paul Johnson) • #13489
Re: QA for Perl
Fri, 2 Aug 2013 11:08:09 +0100
[email protected] (Nicholas Clark) • #13488
RE: QA for Perl
Wed, 31 Jul 2013 21:41:59 +0000
[email protected] (Tracy Radel) • #13487
Re: QA for Perl
Wed, 31 Jul 2013 22:38:15 +0100
[email protected] (David Cantrell) • #13486
Re: QA for Perl
Wed, 31 Jul 2013 23:27:44 +0200
[email protected] (Olof Johansson) • #13485
Re: QA for Perl
Wed, 31 Jul 2013 23:22:59 +0200
[email protected] (Leon Timmermans) • #13484
Re: QA for Perl
Wed, 31 Jul 2013 17:15:50 -0400
[email protected] (Dag Rowe) • #13483
RE: QA for Perl
Wed, 31 Jul 2013 20:46:53 +0000
[email protected] (Tracy Radel) • #13482
Re: QA for Perl
Wed, 31 Jul 2013 16:19:52 -0400
[email protected] (Dag Rowe) • #13481
Re: QA for Perl
Wed, 31 Jul 2013 19:49:08 +0300
[email protected] (Shlomi Fish) • #13480
QA for Perl
Wed, 31 Jul 2013 15:29:18 +0000
[email protected] (Tracy Radel) • #13479
CPAN::Changes::Spec
Tue, 23 Jul 2013 19:19:44 +0200
[email protected] (Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯) • #13478
Re: TAP::Harness and -w
Sun, 7 Jul 2013 19:26:25 +0200
[email protected] (Leon Timmermans) • #13477
Re: TAP::Harness and -w
Sun, 7 Jul 2013 09:00:17 -0700 (PDT)
[email protected] (Ovid) • #13476
Re: TAP::Harness and -w
Sun, 7 Jul 2013 08:11:36 -0700
[email protected] (Karen Etheridge) • #13475
Re: TAP::Harness and -w
Sun, 7 Jul 2013 02:45:22 -0700 (PDT)
[email protected] (Ovid) • #13474
TAP::Parser::Multiplexer isn't parallel on Windows, solutions?
Sat, 6 Jul 2013 18:28:45 -0400
[email protected] (bulk88) • #13473
Re: TAP::Harness and -w
Thu, 4 Jul 2013 18:11:12 -0400
[email protected] (Ricardo Signes) • #13472
Re: TAP::Harness and -w
Thu, 4 Jul 2013 14:33:45 -0700
[email protected] (Eric Wilhelm) • #13471
Re: TAP::Harness and -w
Thu, 4 Jul 2013 16:44:34 -0400
[email protected] (Ricardo Signes) • #13470
Re: TAP::Harness and -w
Thu, 4 Jul 2013 20:04:21 +0200
[email protected] (Leon Timmermans) • #13469
TAP::Harness and -w
Tue, 2 Jul 2013 14:51:11 -0400
[email protected] (Ricardo Signes) • #13468
Re: TPF Devel::Cover grant report May 2013
Mon, 24 Jun 2013 22:52:00 -0400
[email protected] (Ricardo Signes) • #13467
TPF Devel::Cover grant report May 2013
Mon, 24 Jun 2013 00:43:41 +0200
[email protected] (Paul Johnson) • #13466
Re: How might we mark a test suite isn't parallalizable?
Wed, 29 May 2013 10:00:48 -0400
[email protected] (Mark Stosberg) • #13465
Re: How might we mark a test suite isn't parallalizable?
Tue, 7 May 2013 11:05:52 -0700
[email protected] (Buddy Burden) • #13464
Re: How might we mark a test suite isn't parallalizable?
Tue, 7 May 2013 15:17:17 +0100
[email protected] (David Cantrell) • #13463
Re: How might we mark a test suite isn't parallalizable?
Mon, 6 May 2013 13:37:31 -0700
[email protected] (Buddy Burden) • #13462
Re: How might we mark a test suite isn't parallalizable?
Mon, 6 May 2013 12:15:23 +0200
[email protected] (Lasse Makholm) • #13461
Re: How might we mark a test suite isn't parallalizable?
Sun, 5 May 2013 23:03:49 -0700 (PDT)
[email protected] (Ovid) • #13460
Re: How might we mark a test suite isn't parallalizable?
Sun, 5 May 2013 07:07:08 -0400
[email protected] (yary) • #13459
Re: TPF Devel::Cover grant report April 2013
Sat, 4 May 2013 17:40:04 -0400
[email protected] (Ricardo Signes) • #13458
Re: TPF Devel::Cover grant report March 2013
Sat, 4 May 2013 17:37:52 -0400
[email protected] (Ricardo Signes) • #13457
Re: How might we mark a test suite isn't parallalizable?
Sat, 4 May 2013 13:37:38 -0700
[email protected] (Buddy Burden) • #13456
Re: Re: How might we mark a test suite isn't parallalizable?
Fri, 03 May 2013 13:40:24 -0700
[email protected] (chromatic) • #13455
Re: How might we mark a test suite isn't parallalizable?
Fri, 3 May 2013 13:34:35 -0700 (PDT)
[email protected] (Ovid) • #13454
Re: How might we mark a test suite isn't parallalizable?
Fri, 03 May 2013 11:48:19 -0400
[email protected] (Mark Stosberg) • #13453
Re: How might we mark a test suite isn't parallalizable?
Fri, 3 May 2013 16:34:44 +0100
[email protected] (David Cantrell) • #13452
Re: TPF Devel::Cover grant report March 2013
Fri, 03 May 2013 10:32:38 -0500
[email protected] ("Michael G. Schwern") • #13451
Re: How might we mark a test suite isn't parallalizable?
Fri, 03 May 2013 11:03:28 -0400
[email protected] (Mark Stosberg) • #13450
Re: How might we mark a test suite isn't parallalizable?
Fri, 3 May 2013 15:35:07 +0200
[email protected] (Leon Timmermans) • #13449
Re: How might we mark a test suite isn't parallalizable?
Fri, 3 May 2013 13:17:12 +0100
[email protected] (David Cantrell) • #13448
Re: TPF Devel::Cover grant report April 2013
Fri, 03 May 2013 13:30:04 +0200
[email protected] ("Christian Walde") • #13447
Re: TPF Devel::Cover grant report March 2013
Fri, 03 May 2013 13:11:23 +0200
[email protected] ("Christian Walde") • #13446
Re: How might we mark a test suite isn't parallalizable?
Fri, 3 May 2013 11:02:16 +0200
[email protected] (Olivier Mengué) • #13445
TPF Devel::Cover grant report March 2013
Wed, 1 May 2013 22:38:26 +0200
[email protected] (Paul Johnson) • #13444
TPF Devel::Cover grant report April 2013
Wed, 1 May 2013 22:40:17 +0200
[email protected] (Paul Johnson) • #13443
Re: How might we mark a test suite isn't parallalizable?
Thu, 2 May 2013 22:33:06 -0700 (PDT)
[email protected] (Ovid) • #13442
Re: How might we mark a test suite isn't parallalizable?
Thu, 02 May 2013 16:01:23 -0400
[email protected] (Mark Stosberg) • #13441
Re: How might we mark a test suite isn't parallalizable?
Thu, 02 May 2013 15:51:11 -0400
[email protected] (Mark Stosberg) • #13440
Re: How might we mark a test suite isn't parallalizable?
Thu, 2 May 2013 12:51:06 -0700
[email protected] (Karen Etheridge) • #13439
How might we mark a test suite isn't parallalizable?
Thu, 02 May 2013 14:39:13 -0500
[email protected] (brian d foy) • #13438
Re: Smoke Test::More 0.98_05 please.
Sat, 27 Apr 2013 21:49:21 -0400
[email protected] (Ricardo Signes) • #13437
Re: Smoke Test::More 0.98_05 please.
Sun, 28 Apr 2013 01:09:09 +0100
[email protected] (Adrian Howard) • #13436
Re: Smoke Test::More 0.98_05 please.
Sat, 27 Apr 2013 16:32:10 -0700
[email protected] ("Michael G. Schwern") • #13435
Re: Smoke Test::More 0.98_05 please.
Sat, 27 Apr 2013 15:41:16 -0700
[email protected] (Karen Etheridge) • #13434
Re: Smoke Test::More 0.98_05 please.
Sat, 27 Apr 2013 15:22:31 -0700
[email protected] ("Michael G. Schwern") • #13433
Re: Smoke Test::More 0.98_05 please.
Sat, 27 Apr 2013 14:33:21 -0700
[email protected] (Karen Etheridge) • #13432
Re: Smoke Test::More 0.98_05 please.
Sat, 27 Apr 2013 10:19:44 -0400
[email protected] (Ricardo Signes) • #13431
Smoke Test::More 0.98_05 please.
Thu, 25 Apr 2013 10:35:49 -0700
[email protected] ("Michael G. Schwern") • #13430
Re: Post-install tests demo at the qa hackathon \o/
Wed, 24 Apr 2013 09:42:47 +0200 (CEST)
[email protected] (Salve J Nilsen) • #13429
Re: Perl QA Hackathon 2013 / 2014 transition
Fri, 19 Apr 2013 12:35:25 +0100
[email protected] ("Michael G. Schwern") • #13428
Re: Conflicts in the meta spec
Thu, 18 Apr 2013 10:26:23 +0200
[email protected] (Jens Rehsack) • #13427
Re: Perl QA Hackathon 2013 / 2014 transition
Wed, 17 Apr 2013 22:42:17 -0700
[email protected] (Karen Etheridge) • #13426
Re: Perl QA Hackathon 2013 / 2014 transition
Thu, 18 Apr 2013 00:25:16 +0200
[email protected] (Leon Timmermans) • #13425
Re: Conflicts in the meta spec
Wed, 17 Apr 2013 19:43:31 +0100
[email protected] ("Michael G. Schwern") • #13424
Re: Perl QA Hackathon 2013 / 2014 transition
Wed, 17 Apr 2013 16:17:55 +0100
[email protected] ("Michael G. Schwern") • #13423
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.