On 1/27/2022 5:59 PM, Ray Satiro wrote: > You can bisect the issue.
It just occurred to me you will actually have to do a reverse bisect, since you would be looking for when an issue was fixed not when it was broken. git bisect now has terms old and new for that. So for example curl-7_64_1 would be "old" and curl-7_81_0 would be "new", and then you would mark any tested commit with the issue as "old" instead of "bad", and any tested commit without the issue as "new" instead of "good". -- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
