)]}'
{
  "commit": "3f0986b27ce2258e1931a48cdc3e1b4491448d46",
  "tree": "3986caae818f59568e5681fc7268c770a2fde09e",
  "parents": [
    "7d2289a23d969f87dff95d66900adc1ec09a7917"
  ],
  "author": {
    "name": "Patrick Steinhardt",
    "email": "ps@pks.im",
    "time": "Fri Aug 21 08:30:04 2026 +0200"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Fri Aug 21 09:01:54 2026 -0700"
  },
  "message": "builtin/bundle: refactor option handling for progress meter\n\nThe git-bundle(1) command has a couple of command line options that\nrelate to whether or not progress should be reported. These options\nmatch the options that git-pack-objects(1) expects, and consequently\nthey mostly get passed through to it directly.\n\nThis results in somewhat of a confusing interface: there are four\ndifferent options that relate to whether or not progress should be\ndisplayed and how verbose it should be. But in reality, there\u0027s really\nonly two modes:\n\n  - \"--progress\" and \"--all-progress\" result in the same outcome, which\n    is also documented as such.\n\n  - \"--all-progress-implied\" does nothing as we pass that argument to\n    git-pack-objects(1) unconditionally anyway.\n\nSo in the end, the options only control whether or not progress should\nbe displayed at all, nothing else.\n\nRefactor the interface to instead use a simple `progress` boolean. This\nmakes argument handling a lot more straight-forward and it prepares us\nfor the next commit, where we\u0027re migrating git-bundle(1) to the generic\ninterface for generating a packfile.\n\nSigned-off-by: Patrick Steinhardt \u003cps@pks.im\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1e170e92780ed408db8dfefaea1b91d2a6cebe2b",
      "old_mode": 33188,
      "old_path": "builtin/bundle.c",
      "new_id": "bfafadc984e2b69cc064be01c322c9d26ac351d1",
      "new_mode": 33188,
      "new_path": "builtin/bundle.c"
    }
  ]
}