summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-12-29 18:36:41 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-12-29 18:36:41 -0400
commit69650c5989432cd83067614421c6bc3ef0cccab7 (patch)
tree2a04471ea3b769e67eb0e7d99c7f71577b76584e
parent2cc59ae3a1b568f01185bfe251274a4f952f21d8 (diff)
blog for the day
-rw-r--r--doc/design/assistant/blog/day_160__finishing_up_direct_mode.mdwn10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/design/assistant/blog/day_160__finishing_up_direct_mode.mdwn b/doc/design/assistant/blog/day_160__finishing_up_direct_mode.mdwn
new file mode 100644
index 000000000..82484b5c1
--- /dev/null
+++ b/doc/design/assistant/blog/day_160__finishing_up_direct_mode.mdwn
@@ -0,0 +1,10 @@
+A few final bits and peices of direct mode. Fixed a few more bugs in the
+assistant. Made all git-annex commands that don't work at
+all, or only partially work in direct mode refuse to run at all. Also
+some optimisations.
+
+I'll surely need to revisit direct mode later, and make more commands
+support it. `fsck` and `add` especially.
+But the only thing I'd like to deal with before I make a release with direct
+mode is the problem of files being able to be modified while they're
+being transferred, which can result in data loss.