https://bugs.documentfoundation.org/show_bug.cgi?id=101563

--- Comment #24 from raal <r...@post.cz> ---
(In reply to Noel Grandin from comment #23)
> @raal reverting that commit didn't fix this problem for me.
> 
> Are you sure you didn't hit a range of commits when bibisecting?

Hello Noel,
retested again, repo ~/bibisect-win32-5.2

$ git checkout e46c94bf8b05440ece9d69b09c253d9aab6d4f6b
Checking out files: 100% (21872/21872), done.
Previous HEAD position was 1f67051... source
sha:49c2b9808df8a6b197dec666dfc0cda6321a4306
HEAD is now at e46c94b... source sha:19b34c0039c6293f9b37aa70f8055aa2be28ba09

bug is here

$ git checkout HEAD~1
Checking out files: 100% (83/83), done.
Previous HEAD position was e46c94b... source
sha:19b34c0039c6293f9b37aa70f8055aa2be28ba09
HEAD is now at e5c4e40... source sha:fe8896bab01ccb595c993e54866a01f554b54f4f

bug is not here. So bibisect should be correct..

repo ~/bibisect-win32-5.2 is max repo, 1 result contain only 1 commit.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to