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

Re: [PATCH v2] t6026: ensure that long-running script really is

From
Johannes Sixt <j6t@kdbg.org>
Date
Nov 11, 2016, 20:54 UTC
Message-ID
<ba2b3f08-87b1-c954-2020-e5a4bece7f83@kdbg.org>
In-Reply-To
<xmqq60nt3fqc.fsf@gitster.mtv.corp.google.com>
Am 11.11.2016 um 21:48 schrieb Junio C Hamano:
Show 8 quoted lines
> Johannes Sixt <j6t@kdbg.org> writes:
>
>> Good point. Here is an updated version.
>
> Unfortunately, I already took the version before this one and
> started my integration cycle today.  I'll wiggle this in; it
> essentially is about adding a big comment to explain what is going
> on and then moving the when-finished down below it, right?
Correct.

Thank you very much! -- Hannes

Previous: Junio C HamanoNext: Junio C Hamano
Message 7 of 9 in “t6026: ensure that long-running script really is”
  1. t6026: ensure that long-running script really isJohannes Schindelin, Nov 9, 2016
  2. Junio C HamanoNov 10, 2016
  3. Johannes SixtNov 11, 2016
  4. Jeff KingNov 11, 2016
  5. t6026: ensure that long-running script really isJohannes Sixt, Nov 11, 2016
  6. Junio C HamanoNov 11, 2016
  7. Johannes SixtNov 11, 2016
  8. Junio C HamanoNov 11, 2016
  9. Johannes SixtNov 11, 2016

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.