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

Re: [PATCH v7 0/7] coloring test output after traffic signal

From
Adam Spiers <git@adamspiers.org>
Date
Dec 21, 2012, 10:00 UTC
Message-ID
<CAOkDyE8ac0jCutt-hP-p-Bk+PqVda0diXkOANrPbMpT5XTy2GA@mail.gmail.com>
In-Reply-To
<20121221081521.GA22193@sigill.intra.peff.net>
On Fri, Dec 21, 2012 at 8:15 AM, Jeff King <peff@peff.net> wrote:
> On Thu, Dec 20, 2012 at 07:12:31PM -0800, Junio C Hamano wrote:
>> To conclude the bikeshedding discussion we had today, here is what I
>> queued by squashing stuff into relevant patches, so that people can
>> eyeball the result for the last time.
Great, thanks a lot Junio.
> Thanks, this looks OK to me.
To me too.
> And thank you, Adam, for your patience. Seven iterations of color
> bikeshedding is more than should be asked of anyone. :)
;-)
Previous: Jeff King
Message 13 of 13 in “coloring test output after traffic signal”
  1. 0/7 coloring test output after traffic signalJunio C Hamano, Dec 21, 2012
  2. 1/7 tests: test number comes first in 'not ok $count - $message'Junio C Hamano, Dec 21, 2012
  3. 2/7 tests: paint known breakages in yellowJunio C Hamano, Dec 21, 2012
  4. Stefano LattariniDec 21, 2012
  5. Junio C HamanoDec 21, 2012
  6. Stefano LattariniDec 21, 2012
  7. 3/7 tests: paint skipped tests in blueJunio C Hamano, Dec 21, 2012
  8. 4/7 tests: change info messages from yellow/brown to cyanJunio C Hamano, Dec 21, 2012
  9. 5/7 tests: refactor mechanics of testing in a sub test-libJunio C Hamano, Dec 21, 2012
  10. 6/7 tests: test the test framework more thoroughlyJunio C Hamano, Dec 21, 2012
  11. 7/7 tests: paint unexpectedly fixed known breakages in bold redJunio C Hamano, Dec 21, 2012
  12. Jeff KingDec 21, 2012
  13. Adam SpiersDec 21, 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.