Julien Cubizolles <[email protected]> writes: > Julien Cubizolles <[email protected]> writes: > >> Kyle Meyer <[email protected]> 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.
Yep, that's the same commit that I pointed to in the later part of the message you quote, but my guess about what the problematic bits were was wrong. Anyway, should be fixed with b900a85fe. -- Kyle
