Re: [PATCH] cmd_reset: don't trash uncommitted changes unless told to
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jun 27, 2008, 22:11 UTC
- Message-ID
- <7vabh6plyh.fsf@gitster.siamese.dyndns.org>
- In-Reply-To
- <20080627193325.6117@nanako3.lavabit.com>
しらいしななこ <nanako3@lavabit.com> writes:
Show 20 quoted lines
> Quoting Junio C Hamano <gitster@pobox.com>: > >> > Theodore Tso <tytso@mit.edu> writes: >> > ... >> >> 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.
Show 5 quoted lines
> 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.