Bibisecting: Over 1000 bibisects served!

[Norbert Thiebaud]

On Mon, Oct 19, 2015 at 10:47 AM, Stephan Bergmann <sbergman at redhat.com> wrote:
> On 10/19/2015 05:41 PM, Norbert Thiebaud wrote:
>>
>> On Mon, Oct 19, 2015 at 10:16 AM, Stephan Bergmann <sbergman at redhat.com>
>> wrote:
>>>
>>> But that example is irrelevant to what I wrote above, as the commit
>>> message
>>> mentions a range of more than one source commits.
>>>
>> No it is not irrelevant. with the bad bibisect commit, say
>> c49af8fc6406f9e7e8e0b1dcebee6df87bdeb9aa
>> you immediately have the answer you seek:
>>
>> https://gerrit.libreoffice.org/gitweb?p=bibisect-macosx-64-5.0.git;a=commit;h=c49af8fc6406f9e7e8e0b1dcebee6df87bdeb9aa
>
>
> Read what I wrote:  "No, that does not solve the problem *if all you know is
> the commit message of a bibisect commit mentioning a single source commit.*"
> (emphasis added)

Yeah.. and I read the given bugzilla entry too:

Comment 5 Stephan Bergmann 2015-10-19 08:15:34 UTC

(In reply to raal from comment #4)
> This seems to have begun at the below commit.
> Adding Cc: to sbergman at redhat.com ; Could you possibly take a look at this
> one? Thanks
>
> 193ccffc25300d5c26e6f30ab06a2315b6bff879 is the first bad commit
> commit 193ccffc25300d5c26e6f30ab06a2315b6bff879
> Author: Norbert Thiebaud <nthiebaud at gmail.com>
> Date:   Sat Jul 11 20:21:02 2015 -0700
>
>     source sha:c725ebaced006c02baeb9b0ee5ac6ac4625adc01
>
>     source sha:c725ebaced006c02baeb9b0ee5ac6ac4625adc01
>
> author Stephan Bergmann <sbergman at redhat.com> 2015-05-28 21:21:10 (GMT)
> committer Stephan Bergmann <sbergman at redhat.com> 2015-05-28 21:21:10 (GMT)
> commit c725ebaced006c02baeb9b0ee5ac6ac4625adc01 (patch)

raal, please provide either the commit message of the (last good)
commit in the bibisect repo directly preceding this commit, or at
least the URL of the bibisect repo (so I can determine that preceding
commit myself).  (Individual commits in bibisect repos often
correspond to a range of source commits, so it is always important to
know that full range.)

The FULL RANGE here is that single source commit:
c725ebaced006c02baeb9b0ee5ac6ac4625adc01
commit from the bibisect commit 193ccffc25300d5c26e6f30ab06a2315b6bff879

and I know it is a single because it is the only one listed.. if there
was more than one source commit between this bibisect commit and the
previous bibisect commit they would all be listed there, as the
example earlier showed.

the format of my bibisect commit message is:

short message: "source sha:<sha>"  of the last source commit included
followed by a blank line
followed by the list of _all_ source sha included since the previous
bibisect commit (including the one on the short message line)


Norbert