summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar zardoz <zardoz@web>2014-05-13 11:39:49 +0000
committerGravatar admin <admin@branchable.com>2014-05-13 11:39:49 +0000
commit7c0fc5d1baea8b0c00df9b106785b5076d53e010 (patch)
treeff0b69c40e9e142a3aabff20e32716196a25cb8b
parentccd0cbc90d7eadf93d00379138801dd34e5e1664 (diff)
-rw-r--r--doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__.mdwn23
1 files changed, 23 insertions, 0 deletions
diff --git a/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__.mdwn b/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__.mdwn
new file mode 100644
index 000000000..d2610aa6a
--- /dev/null
+++ b/doc/bugs/Revert_to_old_file_version_in_direct_mode___40__VFAT__41__.mdwn
@@ -0,0 +1,23 @@
+### Please describe the problem.
+
+Somewhere on the forums you advised that in order to revert to an old
+version of a file in a direct-mode annex, one should briefly switch to
+indirect mode and check out an earlier revision.
+
+This won’t work though if the direct-mode repo is on a VFAT
+file-system, which does not support indirect mode.
+
+If I didn’t overlook an alternative way, would it make sense to expose
+this functionality in «git annex get $file»? Like «git annex get $file
+--from $repo/$revision»?
+
+Specifying revisions to get from might also be convenient for
+alternative use-cases, I suppose.
+
+Best regards,
+T.
+
+### What version of git-annex are you using? On what operating system?
+
+git-annex 5.20140421
+Linux 3.14.3