Hi,
--------------------------------------------------------------------------------------------------
5e44fec38f33997109bc85c099472b2736649fde is the first bad commit
commit 5e44fec38f33997109bc85c099472b2736649fde
Author: Frederic Gohier <fgohie...@hotmail.com>
Date: Thu May 10 11:12:44 2018 +0100
Fix crash when using musicxml2ly
Issue 5317
Crash when running musicxml2ly
:040000 040000 32b11d27366ff7d629f2b6ca4d250a08293d6ece
750f9ccdbec7fa68babf3f4414aecb70f57c812b M python
--------------------------------------------------------------------------------------------------
So this might be the "currently unknown point in time"?
... I'm sorry, but this does not seem to be correct. It seems Frederic's
commit fixed a crash that made the UTF-8 problem visible because one
could not get to that point before.
So it seems one has to apply Frederic's change to older revisions as
well in order to be able to bisect the UTF-8 problem. Is this possible
with git?
Lukas
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
