On Jul 16, 2004, at 12:48 PM, Stas Bekman wrote:
Without * it won't generate the bullets. I wanted the bullets so * is
there.
Okay.
David
smime.p7s
Description: S/MIME cryptographic signature
On Jul 16, 2004, at 12:45 PM, Stas Bekman wrote:
works fine for me
Okay, will diagnose it from my end.
David
smime.p7s
Description: S/MIME cryptographic signature
On Jul 16, 2004, at 12:44 PM, Stas Bekman wrote:
Because we use Pod::POM with custom callbacks for generating
#fragments. don't use podchecker, use bin/build -l to do links
validation. See bin/build -h for more options.
When DocSet, which powers modperl-docs, was written, the podspec was
unsati
On Jul 16, 2004, at 12:40 PM, Stas Bekman wrote:
Because it's not supported by Pod::POM and wasn't part of the
perlpodspec until recently. Pod::POM detects and auto-links http://
refs on its own, without needing L<>.
Okay.
David
smime.p7s
Description: S/MIME cryptographic signature
David Wheeler wrote:
Hi All,
Still looking at the testing.pod, I see list items like this:
=over
=item * -order=rotate
rotate the tests: a, b, c, a, b, c
=item * -order=repeat
repeat the tests: a, a, b, b, c, c
=item * -order=random
run in the random order, e.g.: a, c, c, b, a, b
=back
I think that
David Wheeler wrote:
% cvs ci -m 'Remove empty list item.' src/docs/general/testing/testing.pod
cvs.apache.org: Connection refused
cvs [commit aborted]: end of file from server (consult above messages if
any)
works fine for me
--
__
S
David Wheeler wrote:
Hi All,
I expect that there was a reason that these links were created as they
were?
% podchecker -nowarnings src/docs/general/testing/testing.pod
*** ERROR: unresolved internal link 'Writing_Tests' at line 89 in file
src/docs/general/testing/testing.pod
*** ERROR: unresolve
David Wheeler wrote:
Why not use L<> for links in the docs?
Because it's not supported by Pod::POM and wasn't part of the
perlpodspec until recently. Pod::POM detects and auto-links http:// refs
on its own, without needing L<>.
--- src/docs/general/testing/testing.pod.~1.33.~Sat May 1 16:53
% cvs ci -m 'Remove empty list item.'
src/docs/general/testing/testing.pod
cvs.apache.org: Connection refused
cvs [commit aborted]: end of file from server (consult above messages
if any)
On Jul 16, 2004, at 10:46 AM, David Wheeler wrote:
Hi All,
Still looking at the testing.pod, I see list items like this:
Oops, wrong list for these questions. Apologies. Moving over to
docs-dev...
Regards,
David
Hi All,
Still looking at the testing.pod, I see list items like this:
=over
=item * -order=rotate
rotate the tests: a, b, c, a, b, c
=item * -order=repeat
repeat the tests: a, a, b, b, c, c
=item * -order=random
run in the random order, e.g.: a, c, c, b, a, b
=back
I think that's generally consider
Hi All,
I expect that there was a reason that these links were created as they
were?
% podchecker -nowarnings src/docs/general/testing/testing.pod
*** ERROR: unresolved internal link 'Writing_Tests' at line 89 in file
src/docs/general/testing/testing.pod
*** ERROR: unresolved internal link
'Usi
Why not use L<> for links in the docs?
--- src/docs/general/testing/testing.pod.~1.33.~ Sat May 1 16:53:19
2004
+++ src/docs/general/testing/testing.pod Fri Jul 16 10:36:15 2004
@@ -3167,7 +3167,7 @@
to test any web application from end to end based application as if it
were a "black box" accep
> When testing for *bugs*, there's certainly a debate about whether to
> skip tests for bugs in older releases (I don't care much are about
> that). For *features*, I don't think there's much to argue about. We
> know this feature works only in 2.0.51 and later, so why test for it in
> earlier r
On Fri, Jul 16, 2004 at 09:08:42AM -0400, Geoffrey Young wrote:
>
> > This makes the test fail against 2.0.50, but it's just a lack-of-feature
> > right, so OK if I half-revert this?
>
> the last time I asked about this, the consensus was that the perl-framework
> is expected to be for developer
> This makes the test fail against 2.0.50, but it's just a lack-of-feature
> right, so OK if I half-revert this?
the last time I asked about this, the consensus was that the perl-framework
is expected to be for developer use only, expected to run (and in some cases
compile) successfully only on c
On Mon, Jul 12, 2004 at 05:03:50PM -, [EMAIL PROTECTED] wrote:
> --- errordoc.t 12 Jul 2004 16:44:47 - 1.2
> +++ errordoc.t 12 Jul 2004 17:03:49 - 1.3
> @@ -59,8 +59,7 @@
> '/redefine/notfound.html code');
>
># 1.3 requires quotes fo
17 matches
Mail list logo
