{"thread":{"id":"13715","subject":"[RFC] Rename git-rm --cached to --index","startedAt":"2008-05-28T23:14:05Z","lastAt":"2008-05-28T23:57:44Z","messageCount":3,"participants":["Nico -telmich- Schottelius","Junio C Hamano","Wincent Colaiuta"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"77985","messageId":"20080528231405.GA25416@denkbrett.schottelius.org","threadId":"13715","inReplyTo":null,"subject":"[RFC] Rename git-rm --cached to --index","fromName":"Nico -telmich- Schottelius","fromEmail":"nico-git-20080529@schottelius.org","sentAt":"2008-05-28T23:14:05Z","receivedAt":"2008-05-28T23:14:05Z","isPatch":false,"sender":{"key":"nico-git-20080529@schottelius.org","avatar":null},"body":"Hello!\n\nI just re-read the git-rm manpage and recognized git-rm knows about\nthe --cached option. As in current git we do not talk about the cache,\nbut about the index, it would imho make sense to rename --cache to\n--index in a user friendly way:\n\n- add --index to git-rm\n- add --index to manpage of git-rm\n- still support --cached in git-rm\n- add hint in manpage that --cached is old naming style\n\nI think naming it --index would make life more consistent for new users\nof git.\n\nNow I'm interested in your opinion ;-)\n\nSincerly\n\nNico\n\nP.S.: As always, please CC me on reply\n\n-- \nThink about Free and Open Source Software (FOSS).\nhttp://nico.schottelius.org/documentations/foss/the-term-foss/\n\nPGP: BFE4 C736 ABE5 406F 8F42  F7CF B8BE F92A 9885 188C\n"},{"id":"77988","messageId":"7vprr6roxt.fsf@gitster.siamese.dyndns.org","threadId":"13715","inReplyTo":"20080528231405.GA25416@denkbrett.schottelius.org","subject":"Re: [RFC] Rename git-rm --cached to --index","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-05-28T23:25:50Z","receivedAt":"2008-05-28T23:25:50Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Please don't make naming inconsistent.  --index means \"do things that\nusually affect only work tree also to the index as well\", while --cached\nmeans \"act only on the index\" (study \"git apply\" for another example).\n\n\"git rm\" that does not touch work tree but removes only the index entry\nshould be named --cached.\n"},{"id":"77994","messageId":"58CD1F67-D406-44BF-A3E2-DB57FD1742EC@wincent.com","threadId":"13715","inReplyTo":"7vprr6roxt.fsf@gitster.siamese.dyndns.org","subject":"Re: [RFC] Rename git-rm --cached to --index","fromName":"Wincent Colaiuta","fromEmail":"win@wincent.com","sentAt":"2008-05-28T23:57:44Z","receivedAt":"2008-05-28T23:57:44Z","isPatch":false,"sender":{"key":"greg@hurrell.net","avatar":"https://avatars.githubusercontent.com/u/7074?v=4"},"body":"El 29/5/2008, a las 1:25, Junio C Hamano escribió:\n> Please don't make naming inconsistent.  --index means \"do things that\n> usually affect only work tree also to the index as well\", while -- \n> cached\n> means \"act only on the index\" (study \"git apply\" for another example).\n>\n> \"git rm\" that does not touch work tree but removes only the index  \n> entry\n> should be named --cached.\n\nI think this is a bit of an arcane distinction. I wonder if a more  \nintuitive scheme might be:\n\n   \"--index\" as it is now (for \"do things that usually affect only  \nwork tree also to the index as well\")\n\nAnd:\n\n   \"--index-only\" for \"act only on the index\"\n\nAlthough the latter is more characters to type than \"--cached\", it is  \na hell of a lot less surprising. For the typing-phobic there's always  \ncompletion.\n\nLet the arguments about bikeshed color and breaking people's scripts  \nensue!\n\nCheers,\nWincent\n"}]}