From 852944f65ec333cb35f6a80be242eac8af1c1d8c Mon Sep 17 00:00:00 2001
From: Runxi Yu
Date: Tue, 24 Mar 2026 03:22:54 +0000
Subject: TODO: Delete done stuff

---
 TODO | 10 ----------
 1 file changed, 10 deletions(-)

(limited to 'TODO')

diff --git a/TODO b/TODO
index 6c48e195..634b3687 100644
--- a/TODO
+++ b/TODO
@@ -1,6 +1,5 @@
 So the to-do list in README.md is more 
 
-* non-atomic batch update semantics
 * how to pass commit graph to hooks
 
 * Receive-pack hook shape redesign; separate post-ref and post-ingest hook
@@ -9,15 +8,6 @@ So the to-do list in README.md is more
 
 * Better status reporting, filling in more things in report-status-v2.
 * Better progress reporting during network operations.
-* More accurate semantics for non-atomic batch updates:
-  - Git validates the batch against the transaction view while
-    we update against the actual store
-  - Duplicates should really just be a fatal transaction level issue
-  - Git basically makes it a single transaction with rejected entries
-    removed, but we basically commit each op separately, so
-    later operations see the live repository after earlier successful
-    ops. So, yeah, atomicity of the surviving subset.
-  - Definitely should stop string matching on errors
 * Design some way to pass commit graphs, or if possible, entire repo
   objects to hooks. Unfortunately this is more difficult than it sounds.
 * Maybe the Progress/Error writers should return error on creation
-- 
cgit v1.3.1-10-gc9f91