Re: RFC: git bisect should accept "paths-to-be-excluded"
- From
Christian Couder <christian.couder@gmail.com>
- Date
- Sep 17, 2013, 09:03 UTC
- Message-ID
- <CAP8UFD1u9hPFcbftpacDFdp27Jmp0YLGbpHPP12uEtjzEmnPQA@mail.gmail.com>
- In-Reply-To
- <vpqvc1z6eoo.fsf@anie.imag.fr>
On Tue, Sep 17, 2013 at 10:21 AM, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:
Show 10 quoted lines
> Christian Couder <christian.couder@gmail.com> writes: > >> In practice though, as git bisect is a kind of binary search, if what >> you want to exclude is exclusively touched by half the commits, it >> will only add one more bisection step if you don't exclude it. > > Actually, I think the same remark would apply to any other Git command > that deal with a set of revisions. If you want to review code with "git > log -p", but you don't care about a subdirectory, you may want a "git > log -p --ignore-dir foo/" or so, too.
Yeah, and there was a patch series about that 2 years ago:
http://thread.gmane.org/gmane.comp.version-control.git/182830/
> And then, the "it's logarithmic" argument doesn't work anymore ;-).
Sure.
Best regards, Christian.