)]}'
{
  "commit": "c3690c97d7b08d9876fcaf0a572b4956bc9b4c33",
  "tree": "3e10ea9c507e0b1adf34479dc43fe2658be9bee0",
  "parents": [
    "e6b09077216ecc1c767506f39be736ba3dcccecb"
  ],
  "author": {
    "name": "Taylor Blau",
    "email": "me@ttaylorr.com",
    "time": "Wed Oct 15 18:28:56 2025 -0400"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Thu Oct 16 10:08:55 2025 -0700"
  },
  "message": "builtin/repack.c: use a string_list for \u0027midx_pack_names\u0027\n\nWhen writing a new MIDX, repack must determine whether or not there are\nany packs in the MIDX it is replacing (if one exists) that are not\nsomehow represented in the new MIDX (e.g., either by preserving the pack\nverbatim, or rolling it up as part of a geometric repack, etc.).\n\nIn order to do this, it keeps track of a list of pack names from the\nMIDX present in the repository at the start of the repack operation.\nSince we manipulate and close the object store, we cannot rely on the\nrepository\u0027s in-core representation of the MIDX, since this is subject\nto change and/or go away.\n\nWhen this behavior was introduced in 5ee86c273b (repack: exclude cruft\npack(s) from the MIDX where possible, 2025-06-23), we maintained an\narray of character pointers instead of using a convenience API, such as\nstring-list.h.\n\nStore the list of MIDX pack names in a string_list, thereby reducing the\nnumber of parameters we have to pass to `midx_has_unknown_packs()`.\n\nSigned-off-by: Taylor Blau \u003cme@ttaylorr.com\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1a79d1d83418ef970986dd913c8750a58dd412c0",
      "old_mode": 33188,
      "old_path": "builtin/repack.c",
      "new_id": "dda533f1716cfaf5ce91a3800d8482a3913d8059",
      "new_mode": 33188,
      "new_path": "builtin/repack.c"
    }
  ]
}