index is a file with multiple uses. E.g., during a conflict it may have 4 "stages". I prefer either index0 or NEXT. On Mon, Jun 13, 2011 at 3:47 PM, Holger Hellmuth <hellmuth@xxxxxxxxxx> wrote: > Am 13.06.2011 14:28, schrieb Junio C Hamano: >>> Jonathan Nieder <jrnieder@xxxxxxxxx> writes: >>>> Do you think it would be valuable to introduce --added as a synonym >>>> for --cached and slowly steer documentation to encourage the latter >>>> in place of the former? > > No. Apart from Junios reason more options won't help that much because > git is already loaded with options (git diff for example has 49). Don't > misinterpret this as a suggestion to remove options, just that an option > in this sea of options must be very obvious to help the casual user. > And "git diff --added" is not telling with what it compares the "added" > files, which means you either know the concept or you have to read the > man page whenever you need to use it. Until you fix it in your memory, > which may be never because you don't use it often enough. > >> It is an entirely different issue that "cached" is _not_ the best way to >> spell "index-only", though. > > Yes, and the one and only word that would be right here (apart from > spelling it out with index-only) is "index", while "index" as used in > git stash and git apply should have been something like 'with-index'. At > least to me '--something' suggests 'something-only' much more than > 'something-too' > > Since this is not possible anymore, we are stuck with 'cache' and > essentially a diff-command that will never be user-friendly. That is why > I still think that an alternate usage with 'git diff wtree index' would > be beneficial, especially with a corresponding 'git put'. > > Holger. > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html