)]}'
{
  "log": [
    {
      "commit": "b066e74393fc5cbfbdb5dac57471b294499f28d9",
      "tree": "8054db96b92aa7728eeb8b65016e699a6a4710b6",
      "parents": [
        "03dbc5d9489d674c37dd10fedd284d5948e9d9ae"
      ],
      "author": {
        "name": "Marc Kupietz",
        "email": "kupietz@ids-mannheim.de",
        "time": "Sun Aug 23 09:57:06 2026 +0300"
      },
      "committer": {
        "name": "Marc Kupietz",
        "email": "kupietz@ids-mannheim.de",
        "time": "Sun Aug 23 09:57:06 2026 +0300"
      },
      "message": "slide timing: per-speaker timing comments activate speaker view pacing\n\nPort the Google-Docs slide workflow convention: timing comments like\n\u003c!-- JD 00:30 --\u003e (speaker code plus MM:SS/HH:MM:SS/seconds duration, or\njust \u003c!-- 00:30 --\u003e for single-speaker talks) are converted into\ndata-timing attributes on the rendered slides\u0027 \u003csection\u003e elements, and\nthe calculated grand total is passed to reveal.js as the totalTime\nconfig value, activating the pacing timer in the speaker view. A\ndocument-supplied totalTime or defaultTiming takes precedence.\n\nA per-speaker time summary is printed during rendering; the new\nslide_timing() function computes slide, speaker, and grand totals\ndirectly from an .Rmd source file without rendering it.\n\nChange-Id: I89d37baab06c6ee8be7ab777a70b9b21295c8780\n"
    }
  ]
}