diff options
| author | 2026-03-24 03:22:54 +0000 | |
|---|---|---|
| committer | 2026-03-24 03:22:54 +0000 | |
| commit | 852944f65ec333cb35f6a80be242eac8af1c1d8c (patch) | |
| tree | 5bf7f24e928a17e960f3d5c067a40966f7503390 /TODO | |
| parent | README: Fix some typos (diff) | |
| signature | No signature | |
TODO: Delete done stuff v0.1.102
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 10 |
1 files changed, 0 insertions, 10 deletions
@@ -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 |
