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

Suggestions to make git easier to understand

From
PVPhilippe Vaucher <philippe.vaucher@gmail.com>
Date
Aug 11, 2011, 07:48 UTC
Message-ID
<CAGK7Mr5T4-DBK7rXeH-1=SNu5HBOEkLBW=CAh5Lhf7oHKjFAiw@mail.gmail.com>
Hello,
The other day I fell on this post:
http://raflabs.com/blogs/silence-is-foo/2011/04/07/staging-area-index-cache-git/

I thought it made some good points about git being kinda confusing, for example sentences like "Changed but not updated" in git status could use a better sentence like "Changed but not in the index". Maybe --cached could have an alias like --index-only for things to be more intuitive as well.

`git rm --index-only somefile` is more understandable than `git rm --cached somefile` imho.

Also, in ls-files, --stage could maybe use an alias like --contents for it to be more self-explanatory.

Philippe

p.s: not saying we should absolutly do what I suggest, but rather start a discussion about how to make git's terminology more intuitive and self-explanatory.

Next: Jonathan Nieder
Message 1 of 6 in “Suggestions to make git easier to understand”
  1. Philippe VaucherAug 11, 2011
  2. Jonathan NiederAug 11, 2011
  3. Junio C HamanoAug 11, 2011
  4. Jonathan NiederAug 11, 2011
  5. Jeff KingAug 12, 2011
  6. Philippe VaucherAug 15, 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.