)]}'
{
  "commit": "6dacff8a2f4d2c24648fb96334fb272b67beff7c",
  "tree": "784152d0101fe5863fd1c480669a5c81375c203c",
  "parents": [
    "eb7892c4019bd5d00175c0eb80eb0c5a47a42ca1"
  ],
  "author": {
    "name": "Indu Bhagat",
    "email": "indu.bhagat@oracle.com",
    "time": "Thu May 23 14:18:23 2024 -0700"
  },
  "committer": {
    "name": "Indu Bhagat",
    "email": "indu.bhagat@oracle.com",
    "time": "Tue Jul 09 10:23:31 2024 -0700"
  },
  "message": "doc: sframe: segregate the ABI/arch-specific components\n\nThe recipe to interpret the SFrame FRE stack offsets is\nABI/arch-specific.\n\nAlthough, there is other information in the specification that is\nABI-specific (like pauth_key usage in AArch64), those pieces of\ninformation are now assimmilated in the SFrame specification in a way\nthat it is fairly difficult to carve then out into a ABI/arch-specific\nsection without confusing the readers.\n\nFor future though, the specification must strive to keep the generic\nparts and ABI/arch-specific parts clearly laid out in separate sections.\n\nlibsframe/\n\t* doc/sframe-spec.texi: Reorder and adapt the contents.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "bb2b35a46d920200a131b081b5d7fc804cec057a",
      "old_mode": 33188,
      "old_path": "libsframe/doc/sframe-spec.texi",
      "new_id": "be5a588be57e125830c9f2113b280884181ec090",
      "new_mode": 33188,
      "new_path": "libsframe/doc/sframe-spec.texi"
    }
  ]
}
