)]}'
{
  "commit": "ddf21ca44a598565afb347d24b7f148703b16be6",
  "tree": "ebf59f8a46e54f705e6bae34d237d4aafa599931",
  "parents": [
    "d4566c84a172f3f9638f7928491fe1be14dca4f7"
  ],
  "author": {
    "name": "Zack Weinberg",
    "email": "zackw@panix.com",
    "time": "Sun Mar 12 19:39:47 2023 -0400"
  },
  "committer": {
    "name": "Zack Weinberg",
    "email": "zackw@panix.com",
    "time": "Sun Mar 12 19:39:47 2023 -0400"
  },
  "message": "bootstrap: Use an absolute path for ACBOOTDIR.\n\nIf we use a relative path for ACBOOTDIR, Automake can’t tell the\ndifference between Autoconf’s configure script’s aclocal.m4\ninclusions (…/m4/*.m4) and the guts of Autoconf\nitself (…/lib/autoconf/*.m4) so it puts both of them into\n$(am__aclocal_m4_deps).  This would be harmless, except that the\nguts-of-Autoconf files are named *relative to $ACBOOTDIR*, which\nmeans Make can’t find them later.  And this is why a build from a\nclean git checkout always starts by regenerating aclocal.m4 and\nconfigure again.\n\nUsing an absolute path for ACBOOTDIR gives automake enough of a clue\nwhat’s going on (see the heuristic circa 5500 of current automake.in,\ncommented “Some modified versions of autoconf don’t use frozen files…”)\nfor it to produce the same value for $(am__aclocal_m4) that it would\nif we were running an installed Autoconf.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "50861367792507b5d703de4f7f140ca9b6058d96",
      "old_mode": 33261,
      "old_path": "bootstrap",
      "new_id": "46e7662e8dffd06853c7df6a65a3b1a3552c2ba4",
      "new_mode": 33261,
      "new_path": "bootstrap"
    }
  ]
}