)]}'
{
  "commit": "5704fc22d0089516eb40dfd7cb398de0d4b9837e",
  "tree": "d5827b211e4513ec4132de1183ae64f97df15f5e",
  "parents": [
    "950f706e31aa236c081a1e8bbb73a0ded170c3d8"
  ],
  "author": {
    "name": "Jakub Kicinski",
    "email": "kuba@kernel.org",
    "time": "Fri Dec 08 10:41:52 2023 -0800"
  },
  "committer": {
    "name": "Daniel Borkmann",
    "email": "daniel@iogearbox.net",
    "time": "Mon Dec 11 09:33:55 2023 +0100"
  },
  "message": "pw-apply: don\u0027t count weekend time in how long patch has been on the list\n\nWe recently started printing a warning when patches are applied\nbefore they spent 24h on the list. The motivation for that was\nto let reviewers from all time zones post their comments.\n\nTo further improve reviewers\u0027 (chances of) work-life balance\nexclude weekend time from the 24h limit, meaning that the\npatch has to spent 24h of work day time on the list. This\nis useful when patches are posted on the list over the weekend\nand even tho they may be 2 days old for someone in the eastern\n/ positive timezones the folks in western / negative timezones\nmost likely haven\u0027t seen them.\n\nThe \"summary\" line for a patch which timeline does not \"straddle\"\nweekend time remains unchanged:\n\n  By: Some Person  Age: 1d 11h  Tree: net-next  Version: 1  Patches: 2\n\nbut if weekend time was in the span (e.g. 10 hours) we\u0027ll see:\n\n  By: Some Person  Age: 1d 1h (+10h)  Tree: net-next  Version: 1  Patches: 2\n\nWe could say something like \"weekend\" next to the plus but its\na long word and my terminals are 80 chars :S\n\nSigned-off-by: Jakub Kicinski \u003ckuba@kernel.org\u003e\nSigned-off-by: Daniel Borkmann \u003cdaniel@iogearbox.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "abf845c5f38b4fec7469bd96e38610be93966007",
      "old_mode": 33188,
      "old_path": "lib.sh",
      "new_id": "2567c568388695b381974df30e710507684e1cf1",
      "new_mode": 33188,
      "new_path": "lib.sh"
    }
  ]
}