devblog

doc/devblog/day_270__distributed_fsck.mdwn

@@ -23,3 +23,5 @@ there's still commit and tree update overhead.
 Probably doesn't make sense to run distributed fscks too often for that and
 other reasons. If the git-annex branch does get too large, there's always
 `git annex forget` ...
+
+**(Update: This was later rethought and works much more efficiently now..)**

doc/devblog/day_272__forest_for_trees.mdwn

@@ -0,0 +1,13 @@
+Rethought distributed fsck. It's not really a fsck, but an expiration of
+inactive repositories, where fscking is one kind of activity. That insight
+let me reimplement it much more efficiently. Rather than updating all
+the location logs to prove it was active, `git annex fsck` can simply and
+inexpensively update an activity log. It's so cheap it'll do it by default.
+The `git annex expire` command then reads the activity log and expires
+(or unexpires) repositories that have not been active in the desired time
+period. Expiring a repository simply marks it as dead.
+
+Yesterday, finished making --quiet really be quiet. That sounds easy,
+but it took several hours. On the `concurrentprogress` branch, I have
+ascii-progress hooked up and working, but it's not quite ready for prime
+time.