From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: Mon, 16 Aug 2010 01:13:51 GMT
Subject: Re: [PATCH] reset: Better warning message on git reset --mixed <paths>
Message-ID: <AANLkTi=ddi_fek3NxF=ESM6HP3Myn6sa1xfsWMyNCUFB@mail.gmail.com>
In-Reply-To: <AANLkTim=TM_3aXMSSN1-vovdc3z6QNR15KHujiJ-wH4_@mail.gmail.com>

On Mon, Aug 16, 2010 at 00:59, Miles Bader <miles@gnu.org> wrote:
> On Mon, Aug 16, 2010 at 5:51 AM, Ævar Arnfjörð Bjarmason
> <avarab@gmail.com> wrote:
>> So it's a question of whether git-reset should do all reset-y things
>> without complaining, even when that infringes on git-checkout's
>> domain.
>
> Of course one question is:  why is this "git-checkout's domain" in the
> first place?
>
> From a UI perspective this functionality doesn't seem to make any more
> sense in checkout -- and perhaps _less_ -- than it does in git-reset.
> "git-checkout <path>" seems like a tacked-on-to-make-cvs-users-happy
> wart rather than a natural part of git-checkout.
>
> I know that as a beginning git user, I always tried to use "git-reset
> --hard <path>", because that sort of made sense in my mental model of
> git commands, only to be confused when it didn't work.  The fact that
> one actually needed to to do git-checkout instead was confusing.

Yeah, maybe one command to reset a file to various states makes more
sense than a singular "checking it out".

Anyway, this is the sort of thing I was alluding to, it won't do to
make micro-changes to the UI without considering the bigger picture.