On Tue, 2014-10-14 at 12:12 +0200, Bjoern Michaelsen wrote:
Since you have the source hash in the build-info.txt file, it might be helpful
to have some script tagging the commit accordingly so that 'git bisect log'
shows the source hashes too.
That would be helpful. However, I would ask for the date to show as
well: the ability to predict "the next step will go forward/backward"
and then to see that happen helps to build confidence.
I have added a paragraph to the wiki page [1,2] asking for source
hashes in the report of results. Would it be worthwhile to provide a
table of source hashes by date linked from that wiki page? Or will
existing versions in the repository be retagged with the additional
info?
Terry.
Links
-----
[1] wiki...HowToBibisect, my change
<https://wiki.documentfoundation.org/index.php?title=QA%2FHowToBibisect&diff=102563&oldid=102562>
[2] wiki...HowToBibisect, current
<https://wiki.documentfoundation.org/QA/HowToBibisect>
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.