Re: Why not git reset --hard <path>?

From: Jacob Keller <jacob.keller@gmail.com>
Date: Sep 28, 2015, 20:53 UTC
Message-ID: <CA+P7+xoTHFL_KU+qBz1KwytxqNTxf1JkjXK7_Ej79uLLnCWD8g@mail.gmail.com>
In-Reply-To: <xmqq612ucm3p.fsf@gitster.mtv.corp.google.com>

On Mon, Sep 28, 2015 at 1:42 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 10 quoted lines

> "George Spelvin" <linux@horizon.com> writes:
>> I understand that "git reset --soft" makes no sense with a path, but
>> why not --hard?
>
> I do not think there is anything fundamentally wrong for wishing for
> "reset --hard <pathspec>".  It probably is just that nobody needed
> it, because "git checkout HEAD <pathspec>" is a 99% acceptable
> substitute for it (the only case where it makes a difference is when
> you added a path to the index that did not exist in HEAD).
>

Personally, I would like to see this simply given the number of times that I use git reset --hard <path> and then realize I should have used git checkout instead. I conceptually think reset --hard should do that, and that checkout is really not meant to do that as a concept.

I may have some time to try and give this a look in the next few days...

Regards, Jake