Re: Git User's Survey 2007 unfinished summary continued

From: Jakub Narebski <jnareb@gmail.com>
Date: Oct 22, 2007, 23:27 UTC
Message-ID: <8fe92b430710221627p6d8a28a3oa0d6f747d99af0b6@mail.gmail.com>
In-Reply-To: <1193064780.4522.142.camel@cacharro.xalalinux.org>

On 10/22/07, Federico Mena Quintero <federico@novell.com> wrote:

Show 6 quoted lines

> On Mon, 2007-10-22 at 09:59 +0200, Andreas Ericsson wrote:
>
>> I doubt many people on this list regularly use git-blame but it's a
>> command that's definitely non-trivial to script out using only the
>> "proper" commands, and CVS/SVN users expect it to be there, so it's
>> probably worth listing anyhow.

> Personally I find git-blame *EXTREMELY* useful.  The workflow is:

Show 8 quoted lines

> 5. "WTF?  Who wrote this crappy code?"
>
> 6. git blame culprit-file.c
>
> 7. "Oh, it was $person with $commit_id... what were they thinking at the
> time?"
>
> 8. git show $commit_id

You don't need blame for that (by the way, as git-blame is slow, you can try -L option to limit range of lines; it is a pity that 'git gui blame' does not support it yet). You can use 'pickaxe search', i.e. "git log -S'<crappy code>'". Sometimes it is better than git-blame...

-- 
Jakub Narebski