Re: [O] recent org-mode changes: completion of repeated tasks reports "10 repeater intervals were not enough to shift date past today"

Another task which gives the same message with SCHEDULED instead of DEADLINE; this one also uses "++" to repeat dates but with no "-0d".  The result looks correct; only the message is bothersome. I replied to the message 'y' twice and then 'n' to test the resulting change.  Changes look fine:

Re: [O] recent org-mode changes: completion of repeated tasks reports "10 repeater intervals were not enough to shift date past today"

Daniel Ortmann writes: > No other tasks.  Here is the complete text with only one url removed: > > * TODO [#C] p6 time entry >   DEADLINE: <2019-01-18 Fri ++1w -0d> >   :PROPERTIES: >   :LAST_REPEAT: [2019-01-11 Fri 17:03] >   :END: >   :LOGBOOK: > > On 1/13/19 10:12 AM, Bernt Hansen wrote: >

Re: [O] recent org-mode changes: completion of repeated tasks reports "10 repeater intervals were not enough to shift date past today"

Daniel Ortmann writes: > I have a weekly scheduled task with ... >   DEADLINE: <2019-01-18 Fri ++1w -0d> > > Recently, when I complete the task it reports the following: > > Clock stopped at [2019-01-11 Fri 17:03] after 0:05 > 10 repeater intervals were not enough to shift date past today.  >

[O] recent org-mode changes: completion of repeated tasks reports "10 repeater intervals were not enough to shift date past today"

I have a weekly scheduled task with ...   DEADLINE: <2019-01-18 Fri ++1w -0d> Recently, when I complete the task it reports the following: Clock stopped at [2019-01-11 Fri 17:03] after 0:05 10 repeater intervals were not enough to shift date past today.  Continue? (y or n) n Thoughts?