From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: git <git@vger.kernel.org>
Subject: Message from git reset: confusing?
Date: Wed, 05 Aug 2009 17:25:23 +0200 [thread overview]
Message-ID: <vpqab2e7064.fsf@bauges.imag.fr> (raw)
Hi,
I was wondering what was the motivation for the output of "git merge":
$ git reset file
file: locally modified
$
I find this message misleading, since it gives me the feeling that
"git reset" errored out because of the file being locally modified (I
also got the remark from a git beginner to whom I was showing the
command: "hey, why didn't it work??").
And indeed, I do not understand the motivation for showing this
message. When I stage content (git add), Git tells me nothing, so why
should it do so when I unstage content? If I want to know the state of
the index after running reset, I'll run "git status" myself ...
I'd suggest adding a -v|--verbose flag to git reset, and default to
being quiet (the already existing -q flag would still be used, to
disable progress indicator). What do other people think?
--
Matthieu
next reply other threads:[~2009-08-05 15:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 15:25 Matthieu Moy [this message]
2009-08-05 17:21 ` Message from git reset: confusing? Junio C Hamano
2009-08-05 17:42 ` Avery Pennarun
2009-08-05 18:07 ` John Tapsell
2009-08-05 18:25 ` Sverre Rabbelier
2009-08-06 9:42 ` Matthieu Moy
2009-08-06 19:21 ` Junio C Hamano
2009-08-07 20:24 ` [PATCH 1/2] Rename REFRESH_SAY_CHANGED to REFRESH_IN_PORCELAIN Matthieu Moy
2009-08-07 20:24 ` [PATCH 2/2 (v2)] reset: make the output more user-friendly Matthieu Moy
2009-08-07 21:20 ` Junio C Hamano
2009-08-08 7:44 ` Matthieu Moy
2009-08-17 17:31 ` Matthieu Moy
2009-08-17 19:50 ` Junio C Hamano
2009-08-21 8:57 ` [PATCH 1/2] Rename REFRESH_SAY_CHANGED to REFRESH_IN_PORCELAIN Matthieu Moy
2009-08-21 8:57 ` [PATCH 2/2 (v3)] reset: make the output more user-friendly Matthieu Moy
2009-08-22 5:44 ` Junio C Hamano
2009-08-22 7:52 ` Matthieu Moy
2009-08-23 2:33 ` Junio C Hamano
2009-08-23 10:42 ` Matthieu Moy
2009-08-23 11:45 ` Reece Dunn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vpqab2e7064.fsf@bauges.imag.fr \
--to=matthieu.moy@imag.fr \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).