• Sources: primary, discussion
  • Summary: The breakage mechanics hold whether or not a reader accepts the argument. SHA-1 and SHA-256 repositories cannot be mixed, submodules must match the parent's format, converting an existing repository invalidates every existing signature and SHA-1 link, and any tool assuming a 40-character hash needs updating. Chacon reports that most Git reimplementation libraries have zero or partial support, and cites an Emily Shaffer talk stating Google may override the new default internally to stay on SHA-1.
  • Why it matters: Anyone maintaining a Git client, host, or CI integration inherits a format migration whose library support Chacon reports as absent or partial.
  • Follow-up: Whether Git 3.0 ships SHA-256 as the default and whether the major reimplementations close the gap first.