Git designed for AI agents.
Merge main (v0.2.0) into p5w-write-path
Federico Elia64b29bbc3582
diff --cc doc/graft/LIMITATIONS.mdindex 4f8fb60,a43c4e0..8dc2e70--- a/doc/graft/LIMITATIONS.md+++ b/doc/graft/LIMITATIONS.md@@@ -149,16 -149,12 +149,19 @@@ Git hooks use privatewritten just before a crash may be missing although the write succeeded.- Custom hooks get the server's `core.fsync` configuration, so the objects thattheir git commands write into a quarantine are durable. When a custom hook- runs with a quarantine, the migration of that quarantine also fsyncs its files,+ runs with a quarantine of the server's own write RPCs (land, commit, merge and+ the other operations), the migration of that quarantine also fsyncs its files,because a hook may write objects without git; that costs about one fsync per- file of the write.+ file of the write. Pushes over SSH or HTTP are different: git's receive-pack+ migrates its own quarantine, so objects that a custom hook writes there+ without git are only as durable as the hook makes them.+- The objects of an update that fails after the quarantine migration remain in+ the repository unreferenced until housekeeping prunes them. They have passed+ the pre-receive hook. Until pruned, they can be read by object ID by anyone+ with read access to the repository. This happens when a land loses its+ compare-and-swap (a batch attempt leaves one pack, an unbatched land loose+ objects), when the expected old revision of a write is stale, and after a+ crash between the migration and the reference update.### Landing (`UserLand`)