Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index 

On 10/19/2015 05:41 PM, Norbert Thiebaud wrote:

On Mon, Oct 19, 2015 at 10:16 AM, Stephan Bergmann <sbergman@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)

Context

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.