Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
In DevelopmentKind: in v2.1.232,
In DevelopmentSection of the release
What
The directory sync path can now build its comparison base from a remote reference by listing the cloned tree with git ls-tree -r -z --full-tree under GIT_NO_LAZY_FETCH=1, and refuses when the tree or commit is not a valid object id.
Details
It reads core.filemode to decide whether file modes from the listing can be trusted.
The stored-base validator now rejects malformed tree references with a message about a sync base naming a path or commit its reader would refuse.
Only the directory sync path uses this; nothing else in the build reaches it.
Evidence
sync base names a path or commit its reader would refuse
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
