Hi Miklos, On Tue, Oct 14, 2014 at 11:49:24AM +0200, Miklos Vajna wrote: > So it's the same as yours, just you need to do 'git show > $sha1:build-info.txt', not 'git show $sha1' if you want to get core.git > hashes.
Not quite (unless Im missing something). Compare e.g.: https://bugs.freedesktop.org/show_bug.cgi?id=84733#c1 with: https://bugs.freedesktop.org/show_bug.cgi?id=81008#c2 Because the bisect log shows the tag names in the latter (source-hash-d6cde02dbce8c28c6af836e2dc1120f8a6ef9932 etc.), I can see from the bugzilla commit what the bisect range is, while I cannot do that with the former (I think) without downloading the whole dbgutil bibisect repo. 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. Best, Bjoern _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
