projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 483bc4f) | patch
gitcli: Document meaning of --cached and --index
authorNanako Shiraishi <nanako3@lavabit.com>
Tue, 1 Jul 2008 14:02:40 +0000 (23:02 +0900)
committerJunio C Hamano <gitster@pobox.com>
Wed, 2 Jul 2008 00:29:38 +0000 (17:29 -0700)
commitaa0c1f2001e6d4fbc48401147541fcf7c84d7a0e
tree714f63a6e7d616481aa929586dd289d9d18de4cdtree | snapshot
parent483bc4f045881b998512ae814d6cf44d0c0cb493commit | diff
gitcli: Document meaning of --cached and --index

We saw this explanation repeated on the mailing list a few times.  Even
though the description of individual options to particular commands are
explained in their manual pages, the reason behind choosing which is which
has not been clearly explained in any of the documentation.

Signed-off-by: Nanako Shiraishi <nanako3@lavabit.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/gitcli.txt diff | blob | history
Git—the stupid content tracker