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

Re: What's cooking in git.git (Feb 2017, #03; Fri, 10)

From
René Scharfe <l.s.r@web.de>
Date
Feb 12, 2017, 23:01 UTC
Message-ID
<2bd2d811-2e2d-1aec-e864-d92c8234fef2@web.de>
In-Reply-To
<36fdf8c9-f82d-4996-09ef-7d718ab3ac41@oracle.com>
Am 12.02.2017 um 19:32 schrieb Vegard Nossum:
Show 5 quoted lines
> I said I would resubmit the patches with more config options and more
> command-line arguments (to avoid potentially breaking backwards
> compatibility), but IIRC the response seemed to be "preceding blank line
> heuristic is good enough" and "why bother", so I ended up not not
> resubmitting anything.

I was (and still am) looking forward to your patches. The current heuristic is simplistic, the patches you already sent improve the output in certain scenarios, my proposed changes on top aimed to limit drawbacks in other scenarios, but together they still have shortcomings.

Avoiding new switches would be nice, though (if possible). I feel we need a lot more tests to nail down our expectations.

René
Previous: Vegard Nossum
Message 5 of 5 in “What's cooking in git.git (Feb 2017, #03; Fri, 10)”
  1. Junio C HamanoFeb 10, 2017
  2. René ScharfeFeb 10, 2017
  3. Junio C HamanoFeb 11, 2017
  4. Vegard NossumFeb 12, 2017
  5. René ScharfeFeb 12, 2017

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.