)]}'
{
  "commit": "ffe8cdf7870bc6a183063d03d38073b3b11caa76",
  "tree": "02278026ad32426d88fd00514207ab1547d3eef1",
  "parents": [
    "3bf541887059e1d19f4d592fff0728ec22e7a952"
  ],
  "author": {
    "name": "Jens Remus",
    "email": "jremus@linux.ibm.com",
    "time": "Tue Nov 10 17:46:02 2026 +0100"
  },
  "committer": {
    "name": "Jens Remus",
    "email": "jremus@linux.ibm.com",
    "time": "Tue Nov 10 17:46:02 2026 +0100"
  },
  "message": "s390: Document operand ordering rules for .insn directive\n\nDocument that operands for the .insn directive are to be specified in\nascending order of their field indices as listed in the Principles of\nOperation manuals.  Composite operands, such as Dx(Bx), Dx(Lx,Bx), and\nDx(Xx,Bx), are treated as a single operand and share the same index.\nExceptions to the ascending index order are noted in the respective\nformat descriptions.\n\ngas/\n\t* doc/c-s390.texi (s390 Formats): Document operand ordering\n\trules for the .insn directive.\n\nSigned-off-by: Jens Remus \u003cjremus@linux.ibm.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a0c7d085ebf6d0b6059ad94688328d96c0d0deed",
      "old_mode": 33188,
      "old_path": "gas/doc/c-s390.texi",
      "new_id": "8cf5718dc38bd372e2a760e43cca6bc36a412672",
      "new_mode": 33188,
      "new_path": "gas/doc/c-s390.texi"
    }
  ]
}
