{"thread":{"id":"54203","subject":"List one hash in \"Some good revs are not ancestors of the bad rev.\"","startedAt":"2020-09-07T15:56:20Z","lastAt":"2020-09-07T15:56:20Z","messageCount":1,"participants":["Paul Menzel"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"405126","messageId":"8a798495-c95e-1690-d5e6-89d1657fdaa4@molgen.mpg.de","threadId":"54203","inReplyTo":null,"subject":"List one hash in \"Some good revs are not ancestors of the bad rev.\"","fromName":"Paul Menzel","fromEmail":"pmenzel@molgen.mpg.de","sentAt":"2020-09-07T15:53:59Z","receivedAt":"2020-09-07T15:56:20Z","isPatch":false,"sender":{"key":"pmenzel@molgen.mpg.de","avatar":null},"body":"Dear git folks,\n\n\nWith\n\n     $ git version\n     git version 2.26.2\n\nduring `git bisect` I got:\n\n> Some good revs are not ancestors of the bad rev.\n> git bisect cannot work properly in this case.\n> Maybe you mistook good and bad revs?\n\nIt would be great, if the (“closest”) conflicting rev could be printed \ntoo, so the user can easily check it.\n\n\nKind regards,\n\nPaul\n"}]}