On 10/19/2015 04:53 PM, Norbert Thiebaud wrote:
On Mon, Oct 19, 2015 at 3:23 AM, Stephan Bergmann <sberg...@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.
No, that does not solve the problem if all you know is the commit
message of a bibisect commit mentioning a single source commit. It
could be a bibisect commit from such a Mac or Windows bibisect repo that
corresponds to a single source commit, or it could be a bibsect commit
from another bibisect repo that may corresponds to a larger range of
source commits.
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
