Re: [PATCH v4] git-send-pack: fix --all option when used with directory

From: Eric Sunshine <sunshine@sunshineco.com>
Date: Mar 31, 2016, 22:55 UTC
Message-ID: <CAPig+cS-Yk7Ey8_+waG7HqG-9BijrQNrtP+0szcgbmVycv_qvQ@mail.gmail.com>
In-Reply-To: <xmqqoa9ul30c.fsf@gitster.mtv.corp.google.com>

On Thu, Mar 31, 2016 at 6:02 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 8 quoted lines

> By the way, for some reason it was unusually painful to find the
> exact breakage by bisecting between maint-2.4 and maint-2.6.  It
> somehow ended up on fingering random places like v2.6.0 itself.
>
> The true culprit is 068c77a5 (builtin/send-pack.c: use parse_options
> API, 2015-08-19).  I didn't dug deep enough to tell if we recently
> broke "git bisect" or if there are something wrong in the shape of
> my history.

I had a similar experience a couple months ago where I was bisecting to find a fix (rather than breakage), and each time I ran bisect, it seemed (randomly) to arrive at a different commit, often a merge, rather than the real fix (which I eventually located by manually examining commits near the commits bisect identified). At the time, I thought I was doing something wrong (and perhaps I was), but your descriptions sounds eerily similar to that experience.

Unfortunately, I no longer recall precisely for what I was searching (other than that someone reported a Git bug which I recalled having been already fixed, and wanted to use bisect to respond with the exact commit which fixed the problem), and the bisect "run" script was throwaway, so I can't consult that for further details.