From: Miles Bader <miles@gnu.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jonathan Nieder" <jrnieder@gmail.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
git@vger.kernel.org, "Ralf Ebert" <info@ralfebert.de>
Subject: Re: [PATCH] reset: Better warning message on git reset --mixed <paths>
Date: Sun, 15 Aug 2010 11:43:59 +0900 [thread overview]
Message-ID: <87tymwzjbk.fsf@catnip.gol.com> (raw)
In-Reply-To: <7vvd7chcj4.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Sat, 14 Aug 2010 18:47:59 -0700")
Junio C Hamano <gitster@pobox.com> writes:
>> warning: --mixed with paths is deprecated; use 'git reset -- <paths>' instead
>
> That sounds helpful.
>
> We've been saying this form is deprecated since 1.5.4; a better
> alternative may be to make this into an error in the next release,
> though.
On a similar note, how about a more helpful error message for
"git reset --hard PATH"? It took me _ages_ to figure out that I
needed to do "git checkout PATH" to get that effect...
e.g.:
$ git reset --hard load-lua.cc
fatal: --hard cannot be used with paths; use "git checkout -- <paths> instead"
-Miles
--
Brain, n. An apparatus with which we think we think.
next prev parent reply other threads:[~2010-08-15 2:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 19:34 [PATCH] reset: Better warning message on git reset --mixed <paths> Ævar Arnfjörð Bjarmason
2010-08-14 21:05 ` Jonathan Nieder
2010-08-15 1:47 ` Junio C Hamano
2010-08-15 2:43 ` Miles Bader [this message]
2010-08-15 8:38 ` Ævar Arnfjörð Bjarmason
2010-08-15 18:36 ` Junio C Hamano
2010-08-15 19:49 ` Jonathan Nieder
2010-08-15 22:18 ` Junio C Hamano
2010-08-15 20:51 ` Ævar Arnfjörð Bjarmason
2010-08-15 22:22 ` Junio C Hamano
2010-08-16 0:59 ` Miles Bader
2010-08-16 1:13 ` Ævar Arnfjörð Bjarmason
2010-08-15 21:05 ` Ralf Ebert
2010-08-16 0:12 ` Jonathan Nieder
2010-08-15 13:02 ` David Fries
2010-08-15 8:43 ` [PATCH v2] " Ævar Arnfjörð Bjarmason
2010-08-16 3:39 ` Junio C Hamano
2010-08-16 4:23 ` Ævar Arnfjörð Bjarmason
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=87tymwzjbk.fsf@catnip.gol.com \
--to=miles@gnu.org \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=info@ralfebert.de \
--cc=jrnieder@gmail.com \
/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).