Thread (4 messages) flat view 4 messages, 2 authors, 2016-06-15

Re: [PATCH] cmd_reset: don't trash uncommitted changes unless told to

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:44:50

Possibly related (same subject, not in this thread)

 しらいしななこ [off-list ref] writes:
Quoting Junio C Hamano [off-list ref]:
quoted
quoted
Theodore Tso [off-list ref] writes:
...
quoted
Stupid quesiton --- where is this documented?  I don't see this
documented either in the man page for git or git-checkout.
You are asking a wrong person.  My git knowledge mostly comes from
yearlong reading of the mailing list articles, and doing a bit myself also
helps ;-).
I couldn't find a good central place to place this as this is more or less
used consistently throughout the UI (log, diff, grep, and then I just
fixed reset as well).

Whereever the description should end up to be in, here is what I think we
should talk about.
Because it is where the convention that is used in all of the UI is
described, I think gitcli documentation is an appropriate place.
I am still not convinced it is the best place but I guess it would be
better than not documenting it anywhere.
Don't you also want to talk about distinction between --cached and
--index that new people are often confused about?  These options are
defined consistently across commands but people who do not know it bring
up discussions to rename --cached to some commands to --index to make it
inconsistent and waste your time every once in a while.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help