git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v6 0/7] make test output coloring more intuitive

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 16, 2012, 23:11 UTC
Message-ID
<7vsj75pp7l.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAOkDyE9B_HfUZmqNqO35mtjTvdihBTiW=uOV2oEQgLUw1xyf=A@mail.gmail.com>
Adam Spiers <git@adamspiers.org> writes:
Show 12 quoted lines
> On Sun, Dec 16, 2012 at 6:54 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> Adam Spiers <git@adamspiers.org> writes:
>>
>>> This series of commits attempts to make test output coloring
>>> more intuitive,...
>>
>> Thanks; I understand that this is to replace the previous one
>> b465316 (tests: paint unexpectedly fixed known breakages in bold
>> red, 2012-09-19)---am I correct?
>
> Correct.  AFAICS I have incorporated all feedback raised in previous
> reviews.
Seemed clean from a cursory look.  Will replace.  Thanks.
Previous: Adam SpiersNext: Jeff King
Message 11 of 18 in “make test output coloring more intuitive”
  1. 0/7 make test output coloring more intuitiveAdam Spiers, Dec 16, 2012
  2. 1/7 tests: test number comes first in 'not ok $count - $message'Adam Spiers, Dec 16, 2012
  3. 2/7 tests: paint known breakages in bold yellowAdam Spiers, Dec 16, 2012
  4. 3/7 tests: paint skipped tests in bold blueAdam Spiers, Dec 16, 2012
  5. 4/7 tests: change info messages from yellow/brown to bold cyanAdam Spiers, Dec 16, 2012
  6. 5/7 tests: refactor mechanics of testing in a sub test-libAdam Spiers, Dec 16, 2012
  7. 6/7 tests: test the test framework more thoroughlyAdam Spiers, Dec 16, 2012
  8. 7/7 tests: paint unexpectedly fixed known breakages in bold redAdam Spiers, Dec 16, 2012
  9. Junio C HamanoDec 16, 2012
  10. Adam SpiersDec 16, 2012
  11. Junio C HamanoDec 16, 2012
  12. Jeff KingDec 20, 2012
  13. Adam SpiersDec 20, 2012
  14. Jeff KingDec 20, 2012
  15. Adam SpiersDec 20, 2012
  16. Junio C HamanoDec 20, 2012
  17. Jeff KingDec 20, 2012
  18. Adam SpiersDec 20, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.