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

Re: [PATCH 0/1] v2.19.0-rc1 Performance Regression in 'git merge-base'

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 30, 2018, 15:26 UTC
Message-ID
<xmqqd0tz7u5p.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<pull.28.git.gitgitgadget@gmail.com>
"Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com> writes:
> As I was testing the release candidate, I stumbled across a regression in
> 'git merge-base' as a result of the switch to generation numbers. The commit
> message in [PATCH 1/1] describes the topology involved,...

I do not recall having seen this kind of updates during the pre-release freeze of previous development cycles, and you are starting a new trend with two findings so far in this cycle. Hopefully this can become a good tradition.

Thanks.
Previous: Jakub NarebskiNext: Jakub Narebski
Message 4 of 5 in “v2.19.0-rc1 Performance Regression in 'git merge-base'”
  1. 0/1 v2.19.0-rc1 Performance Regression in 'git merge-base'Derrick Stolee via GitGitGadget, Aug 30, 2018
  2. 1/1 commit: don't use generation numbers if not neededDerrick Stolee via GitGitGadget, Aug 30, 2018
  3. Jakub NarebskiOct 6, 2018
  4. Junio C HamanoAug 30, 2018
  5. Jakub NarebskiOct 6, 2018

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.