[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AT_BANNER() with empty argument

From: Eric Blake
Subject: Re: AT_BANNER() with empty argument
Date: Mon, 02 Aug 2010 14:07:41 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100720 Fedora/3.1.1-1.fc13 Lightning/1.0b2pre Mnenhy/0.8.3 Thunderbird/3.1.1

On 08/02/2010 01:18 PM, Ralf Wildenhues wrote:
>  * Noteworthy changes in release ?.? (????-??-??) [?]
> +** AT_BANNER() with empty argument will cause visual separation from previous
> +   test cagegory.
> +
>  * Major changes in Autoconf 2.67 (2010-07-21) [stable]

s/cagegory/category/ - also, I've been leaving 1 blank between the * and
first ** line, but two blanks between the last ** and the prior
releases' * line (that is, instead of 2-body-1, swap to 1-body-2 in your

> @@ -23755,9 +23755,8 @@ Writing Testsuites
>  group to run, its output will include a banner containing
>  @var{test-category-name} prior to any tests run from that category.  The
>  banner should be no more than about 40 or 50 characters.  A blank banner
> -will not print, effectively ending a category and letting subsequent
> -test groups behave as though they are uncategorized when run in
> -isolation.
> +indicates uncategorized tests; an empty line will be inserted after
> +tests from an earlier category, effectively ending that category.

Do we mention that categories/blank lines are not printed if tests are
run in parallel?  That is, a using AT_BANNER only affects serial runs.

Other than that, looks okay to me.

Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]