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

Why is there no git-update-cache --modified (aka I give up)

From
MSMarc Singer <elf@buici.com>
Date
Jul 12, 2005, 05:52 UTC
Message-ID
<20050712055218.GA18192@buici.com>
  # git-diff-cache HEAD

is really nice. But, do I really have to invoke git-update-cache with every modified file? I could write a script to cul the filenames from git-diff-cache, but I'm having a hard time believing that that is how others are preparing their commits.

Next: Petr Baudis
Message 1 of 9 in “Why is there no git-update-cache --modified (aka I give up)”
  1. Marc SingerJul 12, 2005
  2. Petr BaudisJul 12, 2005
  3. Junio C HamanoJul 12, 2005
  4. Marc SingerJul 12, 2005
  5. Matthias UrlichsJul 12, 2005
  6. Junio C HamanoJul 12, 2005
  7. diff-stages: support "-u" as a synonym for "-p".Junio C Hamano, Jul 13, 2005
  8. git-diff-*: --name-only and --name-only-z.Junio C Hamano, Jul 13, 2005
  9. Clean up diff option descriptions.Junio C Hamano, Jul 13, 2005

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.