summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joeyh@joeyh.name>2024-04-25 17:01:17 -0400
committerJoey Hess <joeyh@joeyh.name>2024-04-25 17:01:17 -0400
commitd895df10105d20ff708a2f44bd9ac2c9f7aaa5d4 (patch)
tree5b8307ec19e6c0143c9c62ede5d96cf58744843b
parentc410b2bb73345c19d18c7664fd9f48192c4aaa3a (diff)
update
-rw-r--r--doc/todo/git-remote-annex.mdwn4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/todo/git-remote-annex.mdwn b/doc/todo/git-remote-annex.mdwn
index 5693c40da1..05ea923975 100644
--- a/doc/todo/git-remote-annex.mdwn
+++ b/doc/todo/git-remote-annex.mdwn
@@ -9,6 +9,10 @@ Work is in the `git-remote-annex` branch, currently we have a design for
the core data files and operations.
<http://source.git-annex.branchable.com/?p=source.git;a=blob;f=doc/internals/git-remote-annex.mdwn;hb=git-remote-annex>
+Also, that branch has a proof of concept implementation in a shell script.
+Though it doesn't yet use special remotes at all, it is able to do
+incremental pushes to git bundles with a manifest.
+
I still need to do some design work around using the git-annex branch to
detect concurrent push situations where changes to the manifest get lost,
and re-add those changes to it later.