From: Thomas Rast <trast@inf•ethz.ch>
To: Junio C Hamano <gitster@pobox•com>
Cc: <git@vger•kernel.org>
Subject: Re: What's cooking in git.git (Apr 2013, #02; Fri, 5)
Date: Fri, 12 Apr 2013 11:56:11 +0200 [thread overview]
Message-ID: <87ppy0gjic.fsf@linux-k42r.v.cablecom.net> (raw)
In-Reply-To: <7vip40bolc.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Fri, 05 Apr 2013 15:27:11 -0700")
Junio C Hamano <gitster@pobox•com> writes:
> * 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
next prev parent reply other threads:[~2013-04-12 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 22:27 What's cooking in git.git (Apr 2013, #02; Fri, 5) Junio C Hamano
2013-04-07 10:38 ` John Keeping
2013-04-12 9:56 ` Thomas Rast [this message]
2013-04-12 16:05 ` [PATCH 0/4] fix log -L -M Thomas Rast
2013-04-12 16:05 ` [PATCH 1/4] t4211: pass -M to 'git log -M -L...' test Thomas Rast
2013-04-12 16:05 ` [PATCH 2/4] log -L: test merge of parallel modify/rename Thomas Rast
2013-04-12 16:05 ` [PATCH 3/4] log -L: store the path instead of a diff_filespec Thomas Rast
2013-04-12 16:05 ` [PATCH 4/4] log -L: improve comments in process_all_files() Thomas Rast
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ppy0gjic.fsf@linux-k42r.v.cablecom.net \
--to=trast@inf$(echo .)ethz.ch \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox