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

js/early-config, was Re: What's cooking in git.git (Nov 2017, #02; Mon, 6)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Nov 7, 2017, 12:13 UTC
Message-ID
<alpine.DEB.2.21.1.1711071311330.6482@virtualbox>
In-Reply-To
<xmqqfu9rizwc.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Mon, 6 Nov 2017, Junio C Hamano wrote:
Show 6 quoted lines
> * js/early-config (2017-11-03) 1 commit
>  - setup: avoid double slashes when looking for HEAD
> 
>  Correct start-up sequence so that a repository could hang
>  immediately under the root directory again (which was broken at
>  around Git 2.13).

Maybe change that description to avoid the word "hang"? The original report used the very same word "hang", but not for the location of the Git repository: instead, it was used to describe a major latency due to inadvertent network accesses.

I would suggest s/hang/be located/.

Ciao, Dscho

Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 5 in “What's cooking in git.git (Nov 2017, #02; Mon, 6)”
  1. Junio C HamanoNov 6, 2017
  2. js/early-config, was Re: What's cooking in git.git (Nov 2017, #02; Mon, 6)Johannes Schindelin, Nov 7, 2017
  3. Junio C HamanoNov 8, 2017
  4. bp/read-index-from-skip-verification, was Re: What's cooking in git.git (Nov 2017, #02; Mon, 6)Johannes Schindelin, Nov 7, 2017
  5. Junio C HamanoNov 8, 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.