summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-07-20 15:59:25 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-07-20 15:59:25 -0400
commit77b4acc5f95b65c95e6f88960daf44772b73e49f (patch)
treee5137d850ae04599ff581eb42516dfab5b8bb9f4
parent7454853985a838a138e1f0ba94bf20bcf6e0ed1b (diff)
devblog
-rw-r--r--doc/devblog/day_409__--branch.mdwn17
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/devblog/day_409__--branch.mdwn b/doc/devblog/day_409__--branch.mdwn
new file mode 100644
index 000000000..6ede436c7
--- /dev/null
+++ b/doc/devblog/day_409__--branch.mdwn
@@ -0,0 +1,17 @@
+A common complaint is that `git annex fsck` in a bare repository complains
+about missing content of deleted files. That's because in a bare
+repository, git-annex operates on all versions of all files. Today I added
+a --branch option, so if you only want to check say, the master branch, you
+can: `git annex fsck --branch master`
+
+The new option has other uses too. Want to get all the files in the v1.0
+tag? `git annex get --branch v1.0`
+
+It might be worth revisiting the implicit --all behavior for bare
+repositories. It could instead default to --branch HEAD or something like
+that. But I'd only want to change that if there was a strong consensus in
+favor.
+
+Over 3/4th of the time spent implementing --branch was spent in
+adjusting the output of commands, to show "branch:file" is being
+operated on. How annoying.