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

Re: Git status takes too long- How to improve the performance of git

From
MMaryTurner <jamesjohan493@gmail.com>
Date
Nov 24, 2016, 08:38 UTC
Message-ID
<1479976686956-7657457.post@n2.nabble.com>
In-Reply-To
<1479202392275-7657456.post@n2.nabble.com>
Nice

-- View this message in context: http://git.661346.n2.nabble.com/Git-status-takes-too-long-How-to-improve-the-performance-of-git-tp7657456p7657457.html Sent from the git mailing list archive at Nabble.com.

Previous: Heiko VoigtNext: Fredrik Gustafsson
Message 5 of 6 in “Git status takes too long- How to improve the performance of git”
  1. ravalikaNov 15, 2016
  2. Fredrik GustafssonNov 15, 2016
  3. Christian CouderNov 15, 2016
  4. Heiko VoigtNov 15, 2016
  5. MaryTurnerNov 24, 2016
  6. Fredrik GustafssonNov 16, 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.