Geert Kloosterman <g.j.klooster...@gmail.com> writes:
> Hi all,
>
> On Wed, Oct 19, 2011 at 1:17 AM, Viktor Rosenfeld <
> listuse...@googlemail.com> wrote:
>
>
> org-todo-yesterday and org-agenda-todo-yesterday log a note using
> the
> current timestamp and not a timestamp of 23:59 of yesterday's
> date.
>
> I'm using Org-Mode 7.7 pulled today from the git repository.
>
>
>
> I'm experiencing the same problem with the org-mode version I pulled
> from git today.
>
> Switching back to the 7.7 tarball fixes the problem.
>
> Best regards,
> Geert Kloosterman
>
Git bisect identifies the following commit as the source of this
problem.
7d2d8f884b2e22e3056553ea68858fe4fc674427 is the first bad commit
commit 7d2d8f884b2e22e3056553ea68858fe4fc674427
Author: John Wiegley <jo...@newartisans.com>
Date: Sat Aug 13 03:21:49 2011 -0500
Add customization variable `org-use-effective-time'
If non-nil, consider `org-extend-today-until' when creating timestamps.
For example, if `org-extend-today-until' is 8, and it's 4am, then the
"effective time" of any timestamps between midnight and 8am will be
23:59 of the previous day.
:040000 040000 a33f65040163763ed06996b9ffc18bcfc5884457
0782571b08e0a128fa3b072b8b8edf177c001ca3 M lisp
Regards,
Bernt
