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

Re: 'git commit --short' without touching index?

From
Jeff King <peff@peff.net>
Date
Jul 3, 2010, 09:17 UTC
Message-ID
<20100703091748.GA11714@sigill.intra.peff.net>
In-Reply-To
<loom.20100703T102242-536@post.gmane.org>
On Sat, Jul 03, 2010 at 08:30:31AM +0000, Daniel wrote:
Show 7 quoted lines
> 'git commit --short' touches .git/index ('--short' implies '--dry-run').
> 
> Is there any equivalent command that does not touch .git/index?
> 
> I'm using 'git commit --short' in a script to check if the repository needs
> attention.  At present, it touches .git/index, which causes
> unnecessary activity in another script running rsync.

If you are just calling "git commit --short" without arguments (i.e., you care about the current state, not about "what would happen if I commit with these arguments"), then you probably want "git status". Also, you probably should use "git status --porcelain", which is the same as --short but is guaranteed not to change in the future.

However, both "status" and "commit --dry-run" will opportunistically refresh the index. If you don't want to touch the index at all, you can use a combination of:

  # show changes between HEAD and index
  git diff-index HEAD
  # show changes between index and working tree
  git diff-files
  # show untracked files
  git ls-files --exclude-standard -o

One thing you will find, though, is that not refreshing the index means that stat-dirty files (e.g., ones which have no content changed but which have had their timestamps changed) will appear the diff-files above.

I don't think there is a simple way to tell "git status" to refresh the index internally, but not to write it out. It will do this if it doesn't have write permissions, but chmod'ing your index before running the script seems like an awful hack. You could refresh to a temporary index, but that also seems like a hack.

It would be nice if the index-refreshing code only wrote to the index if there was something worth writing. I'm not sure how hard that would be to implement, though.

-Peff
Previous: DanielNext: friedan@muon.rutgers.edu
Message 2 of 7 in “'git commit --short' without touching index?”
  1. DanielJul 3, 2010
  2. Jeff KingJul 3, 2010
  3. friedan@muon.rutgers.eduJul 3, 2010
  4. Junio C HamanoJul 5, 2010
  5. Jeff KingJul 5, 2010
  6. Junio C HamanoJul 5, 2010
  7. Jeff KingJul 6, 2010

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.