Re: [git-users] Highlevel (but simple to implement) commands provided by default for git

From: Duy Nguyen <pclouds@gmail.com>
Date: Jun 3, 2013, 23:22 UTC
Message-ID: <CACsJy8AbhCSSrFnLiS-Gz4GrDiEuK9PM=CGv7fq0pa6Mm6LgRw@mail.gmail.com>
In-Reply-To: <7v38t5sg7k.fsf@alter.siamese.dyndns.org>

On Thu, May 30, 2013 at 3:07 AM, Junio C Hamano <gitster@pobox.com> wrote:

Show 11 quoted lines

> *1* "blame" is an oddball (and I suspect the recent log -Ln,m:path
>     may share the same) in that it really wants a concret path, not
>     a pathspec, so you cannot even say
>
>         cd Documentation; git blame :/Makefile
>
>     I think the right fix is to teach it that the argument it has
>     been taking as a pathname is actually a pathspec, match the
>     pathspec with appropriate place (either in the working tree, or
>     in the commit we start digging from), and use the path that the
>     pathspec matches to a single one (otherwise barf).

You should have CCed me when it's about pathspec :) At least we can safely turn on :/ trick for git-blame and reject other features (like globbing) that blame can't handle. I'll look into how easy/hard to make git-blame support pathspec. -- Duy