summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar graboluk@f6de53961ab0f884e203f602f65eb5cdc0fb7513 <graboluk@web>2015-09-26 02:49:08 +0000
committerGravatar admin <admin@branchable.com>2015-09-26 02:49:08 +0000
commit334408683bbc5b3578df80100677b5d8f70a44be (patch)
treeff69582e55f1ec054c2a6a67f07e1155ad372a70
parent189a2b8313e09f478318134954495f521396ea55 (diff)
-rw-r--r--doc/forum/what_are___95__exactly__95___limitations_of_git-annex_when_using_it_like_dropbox.mdwn6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/forum/what_are___95__exactly__95___limitations_of_git-annex_when_using_it_like_dropbox.mdwn b/doc/forum/what_are___95__exactly__95___limitations_of_git-annex_when_using_it_like_dropbox.mdwn
new file mode 100644
index 000000000..276ba646e
--- /dev/null
+++ b/doc/forum/what_are___95__exactly__95___limitations_of_git-annex_when_using_it_like_dropbox.mdwn
@@ -0,0 +1,6 @@
+I'm trying to migrate from dropbox to git-annex. But I'm learning that git-annex has "limitations", as in
+"but it can be used to sync files such a way, with certain limitations". So what exactly are these limitations? I've learned already the hard way that newline can't be a character in a filename, and apparently git directories can't be synced?
+
+These are two big issues imo (especiall the second one) - right now I don't have any filenames with newlines, and no git directories, but the brilliant thing about dropbox is that I don't have to think about such things, everything gets synced.
+
+But in any case, if I'm to use git-annex as a dropbox replacement, I really need to know what precisely are its limitations, so that it doesn't become an issue in two months out of nowhere...