summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-01-06 18:00:42 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-01-06 18:00:42 -0400
commitd37a7c019f594f58350abdd37800e04ff5229ce6 (patch)
tree8638beca7f58ce44c57f6cc8eea8edec0f778bf0
parent47d55e3d1f7ac6eed2f5596e697360705559c537 (diff)
debblugh
-rw-r--r--doc/devblog/day_244__relative_paths.mdwn14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/devblog/day_244__relative_paths.mdwn b/doc/devblog/day_244__relative_paths.mdwn
new file mode 100644
index 000000000..f631dbc8f
--- /dev/null
+++ b/doc/devblog/day_244__relative_paths.mdwn
@@ -0,0 +1,14 @@
+git-annex internally uses all absolute paths all the time.
+For a couple of reasons, I'd like it to use relative paths.
+The best reason is, it would let a repository be moved while git-annex was
+running, without breaking. A lesser reason is that Windows has some
+crazy small limit on the length of a path (260 bytes?!), and using relative
+paths would avoid hitting it so often.
+
+I tried to do this today, in a `relativepaths` branch. I eventually got the
+test suite to pass, but I am very unsure about this change. A lot of random
+assumptions broke, and the test suite won't catch them all. In a few
+places, git-annex commands do change the current directory, and that
+will break with relative paths.
+
+A frustrating day.