On Mon, Oct 19, 2015 at 3:23 AM, Stephan Bergmann <sbergman@redhat.com> wrote:
A reminder when updating a bug with information about a successful
bibisecting: Do not only paste the commit message of the first bad bibisect
repo commit, but: "please [also] provide either the commit message of the
(last good) commit in the bibisect repo directly preceding this [first bad]
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.)"
(<https://bugs.documentfoundation.org/show_bug.cgi?id=91895#c5>)
on Mac and Windows bibisect, the bibisect commit list all the source
commit sha since the previous bibisect commit,
hence solving that problem.
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.