Re: What's cooking in git.git (Apr 2013, #02; Fri, 5)

From: Thomas Rast <trast@inf.ethz.ch>
Date: Apr 12, 2013, 09:56 UTC
Message-ID: <87ppy0gjic.fsf@linux-k42r.v.cablecom.net>
In-Reply-To: <7vip40bolc.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

Show 12 quoted lines

> * tr/line-log (2013-04-05) 7 commits
>   (merged to 'next' on 2013-04-05 at 5afb00c)
>  + log -L: fix overlapping input ranges
>  + log -L: check range set invariants when we look it up
>   (merged to 'next' on 2013-04-01 at 5be920c)
>  + Speed up log -L... -M
>  + log -L: :pattern:file syntax to find by funcname
>  + Implement line-history search (git log -L)
>  + Export rewrite_parents() for 'log -L'
>  + Refactor parse_loc
>
>  Will merge down to 'master'

I did some fuzz-testing, choosing random commits and ranges from files and running log -L on them.

While the good news is that I couldn't break ordinary log -L, there's a rather embarassing pair of bugs: -M is completely broken (at least when it would do any good) and the tests that claim to look at move support actually don't pass -M.

So please hold off merging, I'll try to get this fixed this weekend.

Sorry for the trouble!

-- 
Thomas Rast
trast@{inf,student}.ethz.ch