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

Re: [PATCH 2/2] Fix t3404 assumption that `wc -l` does not use whitespace.

From
Junio C Hamano <gitster@pobox.com>
Date
May 15, 2008, 17:18 UTC
Message-ID
<7vr6c3h4eb.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20080515112030.GA12781@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 9 quoted lines
> On Thu, May 15, 2008 at 11:16:27AM +0100, Mike Ralphson wrote:
>
>> Which branch(es) would it be most useful on which to have this
>> automated build/test cycle?
>
> I would think maint, master, and next, but with next as the least
> important. I think Junio generally tests maint and master before
> publishing, but presumably not always next (as there was test breakage
> in next earlier today).

I'd prefer heterogeneous automated test coverage to be on 'next' and 'master'. If the coverage extends to 'maint' that would be nicer, but on the other hand, I rarely apply anything remotely questionable directly on top of maint (instead, I'd fork from maint and merge the result first to next or master), so if we can catch master and next, we should be Ok.

Before any push-out, I ran tests on all four integration branches on Debian (etch) and FC (I think it is FC5), both x86-64. But sometimes 'pu' is shipped with known breakage in tests. I can not push out with broken tests in 'maint', 'master' or 'next' (automated procedure on my end prevents me from doing so).

Previous: Jeff KingNext: Mike Ralphson
Message 11 of 23 in “Fix t3404 assumption that `wc -l` does not use whitespace.”
  1. 2/2 Fix t3404 assumption that `wc -l` does not use whitespace.Brian Gernhardt, Apr 27, 2008
  2. Johannes SchindelinApr 27, 2008
  3. Brian GernhardtApr 27, 2008
  4. Jeff KingApr 28, 2008
  5. Mike RalphsonApr 28, 2008
  6. Jeff KingMay 13, 2008
  7. Mike RalphsonMay 13, 2008
  8. Mike RalphsonMay 15, 2008
  9. Jeff KingMay 15, 2008
  10. Jeff KingMay 15, 2008
  11. Junio C HamanoMay 15, 2008
  12. Mike RalphsonMay 16, 2008
  13. Brian GernhardtApr 28, 2008
  14. Junio C HamanoApr 27, 2008
  15. Johannes SchindelinApr 28, 2008
  16. Jörg SommerApr 28, 2008
  17. Johannes SchindelinApr 28, 2008
  18. Jörg SommerApr 28, 2008
  19. Johannes SchindelinApr 28, 2008
  20. Junio C HamanoApr 28, 2008
  21. Johannes SchindelinApr 28, 2008
  22. Junio C HamanoApr 28, 2008
  23. Johannes SchindelinApr 28, 2008

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.