Julien Cubizolles <j.cubizol...@free.fr> writes:

> Kyle Meyer <k...@kyleam.com> writes:
>
>
>> Since you have the git repo set up and have a good/bad range, you can use
>> git bisect to find the offending commit.

I finally found the offending commit,

it's commit 4f578a3f7fe193229adc239c93d6983bcc030d41 org-agenda: Small
refactoring by N. Goaziou.

Julien.



Reply via email to