git reset [--mixed] without --quiet refreshes the index in order to
display the Unstaged changes after reset. When --quiet is given,
that output is suppressed, removing the need to refresh the index.
Other porcelain commands that care about a refreshed index should
already be refreshing it, so
On Wed, Jan 09, 2013 at 12:16:13AM -0800, Martin von Zweigbergk wrote:
git reset [--mixed] without --quiet refreshes the index in order to
display the Unstaged changes after reset. When --quiet is given,
that output is suppressed, removing the need to refresh the index.
Other porcelain
On Wed, Jan 9, 2013 at 9:01 AM, Jeff King p...@peff.net wrote:
On Wed, Jan 09, 2013 at 12:16:13AM -0800, Martin von Zweigbergk wrote:
git reset [--mixed] without --quiet refreshes the index in order to
display the Unstaged changes after reset. When --quiet is given,
that output is suppressed,
On Wed, Jan 9, 2013 at 11:12 AM, Junio C Hamano gits...@pobox.com wrote:
Martin von Zweigbergk martinv...@gmail.com writes:
And as a Porcelain, I would rather expect it to leave the resulting
index refreshed.
Yeah, I guess you're right. Regular users (those using only porcelain)
shouldn't
Martin von Zweigbergk martinv...@gmail.com writes:
There is a test case in t7102 called '--mixed refreshes the index',
but it only checks that right output it printed.
I think that comes from 620a6cd (builtin-reset: avoid forking
update-index --refresh, 2007-11-03). Before that commit, we
5 matches
Mail list logo
