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

Re: [PATCH] t5551: fix the 50,000 tag test

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 10, 2014, 05:53 UTC
Message-ID
<xmqqoay1b99g.fsf@gitster.dls.corp.google.com>
In-Reply-To
<53967F48.1080103@web.de>
Torsten Bögershausen <tboegi@web.de> writes:
> Thanks for digging, as we now know better:
> do you want to squeeze in someting like this:
>
> s/Since the day/Since commit 5e2c7cd2/ 

I usually do not dig only to give suggestions to others, which will risk the time I spent to go to total waste. When I find the log message lacking, and if the patch looked otherwise OK enough, I do the digging myself in order to tweak to reduce one round-trip (otherwise I'd just discard and tell the submitter to do the digging). I may send out what I learned as a response, but that is a mere "side effect"; the primary effect of queuing an improved patch has often already happened when you see the result of my digging.

I do not recall what I did for this particular patch, but you should be able to fetch and run "git log origin/master..origin/pu" to find out what I did ;-).

Thanks.
Previous: Torsten Bögershausen
Message 4 of 4 in “t5551: fix the 50,000 tag test”
  1. t5551: fix the 50,000 tag testTorsten Bögershausen, Jun 5, 2014
  2. Junio C HamanoJun 9, 2014
  3. Torsten BögershausenJun 10, 2014
  4. Junio C HamanoJun 10, 2014

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.