)]}'
{
  "commit": "6822cbef346e21ff891347784e144bc429d4b777",
  "tree": "303355c55bb3a951b5cbbf938987bda499c6573e",
  "parents": [
    "93c1f0610de4561db69b3f4bace639c034bc370f"
  ],
  "author": {
    "name": "Alex Konradi",
    "email": "akonradi@fuchsia.infra.roller.google.com",
    "time": "Fri Jul 28 19:28:51 2023 +0000"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Fri Jul 28 12:30:32 2023 -0700"
  },
  "message": "[roll] Roll fuchsia [netstack3] Provide summary for socketmap addr tag\n\nInstead of making the entire address vector available to socket\nimplementations for the purpose of computing the per-address tag values,\nonly provide a summary of the information. The tag computation doesn\u0027t\nneed to know, for example, whether a connected socket with a device\nbound is bound to a loopback vs ethernet device, just that there is one.\n\nThis has the happy follow-on effect of letting us get rid of the\n`Bound\u003cS\u003e : Tagged\u003cAddrVec\u003cI, D, A\u003e\u003e` bounds that were annoyingly viral\nand therefore everywhere. Since there is a blanket impl in terms of `S:\nSocketMapStateSpec`, that bound can now just be inferred.\n\nOriginal-Bug: 21198\nOriginal-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/891172\nOriginal-Revision: d568c462817915921372043967224aa39ed9b08a\nGitOrigin-RevId: f47bf3204de7e9416d89c03f85df53946a5fbc6b\nChange-Id: I425a828ab6b8d169c937fd75c38f8593e20d773a\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "dc56840b2a292a0d4cd676a8465fc9aecb802da3",
      "old_mode": 33188,
      "old_path": "stem",
      "new_id": "869fbb114cf2095c4c726ed2deee9b36206fc79f",
      "new_mode": 33188,
      "new_path": "stem"
    }
  ]
}