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

Re: [PATCH] t7300: fix broken && chains

From
erik elfström <erik.elfstrom@gmail.com>
Date
Sep 1, 2015, 06:31 UTC
Message-ID
<CAMpP7NZMMYyCbmnzhLTqa73TD_mqk+rO8=D0v9qb0z_UmBQ-rg@mail.gmail.com>
In-Reply-To
<xmqqzj17wg1i.fsf@gitster.mtv.corp.google.com>
On Mon, Aug 31, 2015 at 6:58 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 13 quoted lines
>
> Many of the constructs we see here shows clearly that this is an
> ancient part of the codebase ;-), as we would be using the one
> parameter form of "git init" and more test_* helpers if we were
> writing this script in today's Git codebase.  It may have been
> better if you didn't do "while we are here" and corrected only the
> &&-chain in patch 1/2 and then updated the style of the tests to
> take advantage of the newer facilities recent test-lib has in a
> separate patch 2/2, but this will do at least for now.
>
> Will queue.
>
> Thanks.

I can do a re-roll with the chain fix in the first patch and a more thorough modernization of t7300 in separate patches if you'd like? I almost went this way for v1 but decided to limit the scope for the first version.

(Forgot to include the list in my first reply, sorry... And forgot to turn off HTML in the second... sigh, sorry for the spam)

/Erik
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 7 in “t7300: fix broken && chains”
  1. t7300: fix broken && chainsErik Elfström, Aug 30, 2015
  2. Junio C HamanoAug 31, 2015
  3. erik elfströmSep 1, 2015
  4. Junio C HamanoSep 1, 2015
  5. Jeff KingAug 31, 2015
  6. erik elfströmSep 1, 2015
  7. Jeff KingSep 1, 2015

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.