)]}'
{
  "commit": "fbf3d0669f830b4492070aa33f57dbf2c43fa4c8",
  "tree": "b9da3fc3c190a01490f8d8f9fd0c724108976e7c",
  "parents": [
    "f368df439b31b422169975cc3c95f7db6a46eada"
  ],
  "author": {
    "name": "Kristoffer Haugsbakk",
    "email": "code@khaugsbakk.name",
    "time": "Thu Nov 20 17:26:49 2025 +0100"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Thu Nov 20 10:03:31 2025 -0800"
  },
  "message": "doc: warn against --committer-date-is-author-date\n\nThis option could create a commit history which violates the assumption\nthat commits have non-decreasing commit timestamps. Warn against that in\nboth git-am(1) and git-rebase(1).\n\nThe genesis of this option is from git-am(1) and was added in\n3f01ad66 (am: Add --committer-date-is-author-date option,\n2009-01-22). The commit message doesn’t give us an example\nof a use case, but the thread starter does:[1]\n\n    I\u0027ve a big set of patches in a mbox file: there\u0027s sufficient info\n    inside for git-am to work.\n\n    Yet, each time I do import these, my sha1sums are changing because of\n    different commit dates.\n\n    I\u0027d like to force the commit date to match the info/date from the time\n    I received the email (and therefore always get back the right\n    sha1sums).\n\n[1]: https://lore.kernel.org/git/46d6db660901221441q60eb90bdge601a7a250c3a247@mail.gmail.com/\n\nSo the motivation was to treat git-am(1) as an import command that\ncreates the same commit IDs.\n\nPutting aside the question of whether you should be using git-am(1) for\nimporting commits, this approach is problematic:\n\n• you still need to apply the commits to the same base if you want the\n  same hashes; and\n• you need the same committer.\n\nAnd if you expect the same committer, why is this person applying the\nsame patches multiple times with the goal of making *identical* commits?\n\nThat was all for git-am(1).\n\nIt was added to git-rebase(1) in 570ccad3 (rebase: add options passed to\ngit-am, 2009-03-18)[2] in order to plug options that could not be sent\non to git-am(1). At this point the utility of the option graduated to\nmaking no sense; a use case for `git rebase --committer-date-is-author-\ndate` is still yet to be found.\n\nJust warn against using this option on both commands and remind the user\nto consider whether they really need it.\n\n† 2: See also 7573cec5 (rebase -i: support\n     --committer-date-is-author-date, 2020-08-17) for the commit for the\n     merge backend\n\nSuggested-by: Johannes Sixt \u003cj6t@kdbg.org\u003e\nSigned-off-by: Kristoffer Haugsbakk \u003ccode@khaugsbakk.name\u003e\nAcked-by: Johannes Sixt \u003cj6t@kdbg.org\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "221070de4812276171b494017e22fb6e4bff543a",
      "old_mode": 33188,
      "old_path": "Documentation/git-am.adoc",
      "new_id": "264d21a7de780122af88087aad0cdc2f06551a6c",
      "new_mode": 33188,
      "new_path": "Documentation/git-am.adoc"
    },
    {
      "type": "modify",
      "old_id": "956d3048f5a6189f254ada226f47e9ccba3609fc",
      "old_mode": 33188,
      "old_path": "Documentation/git-rebase.adoc",
      "new_id": "0f808c82b2877b41a4401090ccb498fe2b13efca",
      "new_mode": 33188,
      "new_path": "Documentation/git-rebase.adoc"
    }
  ]
}