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

Re: git rm --cached should be git rm --cache or git rm --stage

From
ZHZenaan Harkness <zen@freedbms.net>
Date
Aug 20, 2016, 07:25 UTC
Message-ID
<20160820072500.GC24992@x220-a02>
In-Reply-To
<20160820072214.GB24992@x220-a02>
   Please CC me :)
Show 14 quoted lines
> From man git-rm:
> 
> --cached
>   Use this option to unstage and remove paths only from the index.
>   Working tree files, whether modified or not, will be left alone.
> 
> 
> This wording is unclear and dangerous, and ought be cleaned up somehow.
> 
> Probably also the option name should change.
> 
> See here for examples of community self-help compensating for git-rm man
> page's particularly bad wording:
> http://stackoverflow.com/questions/6919121/why-are-there-2-ways-to-unstage-a-file-in-git

Also, perhaps a git porcelain command "git unstage" to unstage staged changes. Something small like this might make a huge difference for git newbies.

Previous: Zenaan HarknessNext: Junio C Hamano
Message 2 of 6 in “git rm --cached should be git rm --cache or git rm --stage”
  1. Zenaan HarknessAug 20, 2016
  2. Zenaan HarknessAug 20, 2016
  3. Junio C HamanoAug 20, 2016
  4. Philip OakleyAug 20, 2016
  5. Zenaan HarknessAug 20, 2016
  6. Philip OakleyAug 20, 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.