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

Re: speed of git reset -- file

From
Joey Hess <joey@kitenet.net>
Date
Jun 1, 2011, 20:16 UTC
Message-ID
<20110601201629.GA25354@gnu.kitenet.net>
In-Reply-To
<20110601195831.GA30070@sigill.intra.peff.net>
Jeff King wrote:
Show 6 quoted lines
> So implementing the "optimization" to drop the refresh here doesn't seem
> worth it. It inroduces an awful inconsistency, and it probably isn't
> saving much in practice. Lots of other commands will end up stat'ing
> everything, anyway. Users with giant repos or slow stat calls are
> probably better off using assume-unchanged, which would help this and
> many other situations.

Sounded like git-reset -q file could be optimised to not reread the index without any visible inconsistency?

My experience with semi-large trees[1] is that I have to remember to use "git status ." in a subdir; that "git commit -a" is of course slow when I need to use it; and that the index gets big and things that need to update it can become somewhat slow especially on slow disks, but that otherwise git scales fairly well and has good locality, and that it's easy to reason about what operations are global and avoid them. So this git-reset behavior was surprising.

assume-unchanged seems like it would add a lot of work when merging.
-- 
see shy jo

[1] Two or three times the number of files as linux-2.6.
Previous: Jeff KingNext: Jeff King
Message 9 of 17 in “speed of git reset -- file”
  1. Joey HessMay 31, 2011
  2. Jeff KingMay 31, 2011
  3. Junio C HamanoMay 31, 2011
  4. Jeff KingMay 31, 2011
  5. Matthieu MoyMay 31, 2011
  6. Nguyen Thai Ngoc DuyJun 1, 2011
  7. Junio C HamanoMay 31, 2011
  8. Jeff KingJun 1, 2011
  9. Joey HessJun 1, 2011
  10. Jeff KingJun 1, 2011
  11. Joey HessJun 1, 2011
  12. Jeff KingJun 1, 2011
  13. Joey HessJun 1, 2011
  14. Jeff KingJun 2, 2011
  15. Joey HessJun 2, 2011
  16. Joey HessJun 2, 2011
  17. Junio C HamanoJun 1, 2011

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.