Eric.
You know, I really appreciate your effort. I do. Now to the substance of it.
1. Now that I know the bandwidth limitations and constraints I will be much
more careful in transmitting files. I did not know before. I know now. I
will take care to determine what compression format to use prior
On 06/02/2015 02:05 PM, Arthur Schwarz wrote:
>>
>> On 06/02/2015 11:59 AM, Arthur Schwarz wrote:
>>
>> I haven't yet seen any pdf, so it's hard for me to state what you are
>> referring to.
>
>
> Both .pdf and .odt files are included in this post.
Uggh. That resulted in your mail being 2
On 06/02/2015 11:59 AM, Arthur Schwarz wrote:
> I appreciate your comments. The TAP pdf that I sent you is part of a larger
> document. At the moment the document is 48 pages and is a complete
> replacement for Section 15 up to dejaGnu which I haven't started yet. The
> pdf was sent in lieu of the
On 2015-06-02 09:40 -0700, Arthur Schwarz wrote:
> [Nick Bowler wrote]
> The plan line has to be mandatory for this feature to work as
> intended (i.e., for the TAP consumer to determine whether a
> producer has run to completion or not). An optional plan would
> be useless.
>
>
I appreciate your comments. The TAP pdf that I sent you is part of a larger
document. At the moment the document is 48 pages and is a complete
replacement for Section 15 up to dejaGnu which I haven't started yet. The
pdf was sent in lieu of the Open Office document, which is the genesis of
the pdf.
On 2015-06-02 09:40 -0700, Arthur Schwarz wrote:
> [Nick Bowler wrote]
> The plan line has to be mandatory for this feature to work as
> intended (i.e., for the TAP consumer to determine whether a
> producer has run to completion or not). An optional plan would
> be useless.
>
> S
On 06/02/2015 10:24 AM, Arthur Schwarz wrote:
> A coupla' issues. I don't know Texinfo. I have included an extensive
> revision of the TAP testing cycle as a pdf file, downloaded from an Open
> Office Document.
While that may work, it is tedious to maintainers. We have to figure
out which text yo
The plan line has to be mandatory for this feature to work as
intended (i.e., for the TAP consumer to determine whether a
producer has run to completion or not). An optional plan would
be useless.
Sorry to be such a pest.
Your statement that "... determine whether a producer has
A coupla' issues. I don't know Texinfo. I have included an extensive
revision of the TAP testing cycle as a pdf file, downloaded from an Open
Office Document. And, the only reason that I started rewriting the test
section was that I couldn't understand what was written and thought that if
I had to
On 2015-06-01 14:17 -0700, Arthur Schwarz wrote:
> The .trs tag :global-test-result: should be :test-global-result:.
>
> 15.3.3.2 Log files generation and test results recording
> :test-global-result:
[...]
> === .trf ===
> :global-test-result: FAIL
Indeed, this is an error in the manual
On Saturday 18 of April 2015 11:50:31 Pavel Raiskup wrote:
> On Friday 17 of April 2015 18:07:57 Peter Rosin wrote:
> > On 2015-04-17 17:54, Pavel Raiskup wrote:
> > > I tried to prepare the patch, but thats probably wrong. It would be nice
> > > if somebody could comment,
> >
> > Microsofts arch
On 2015-06-01 14:45 -0700, Arthur Schwarz wrote:
> http://testanything.org/
>
> Explicitly specifies that a test plan is optional.
[...]
> The operand part of this paragraph is " The plan is optional ..." which
> directly contradicts "It must appear once ...". Your diagnostic message is
> either i
12 matches
Mail list logo
