summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/bugs/amd64_i386_standalone:_no_SKEIN/comment_1_fcf7e1089b25993378df7574ccee8062._comment8
-rw-r--r--doc/bugs/interference_with_Dropbox_results_in_data_loss/comment_2_fe852adc1d7d3062ace269ceb134f3ad._comment8
-rw-r--r--doc/tips/do_not_use_git-annex_inside_your_Dropbox.mdwn5
-rw-r--r--doc/todo/Provide_a___34__git_annex_satisfy__95__num__95__copies__34___command.mdwn9
4 files changed, 30 insertions, 0 deletions
diff --git a/doc/bugs/amd64_i386_standalone:_no_SKEIN/comment_1_fcf7e1089b25993378df7574ccee8062._comment b/doc/bugs/amd64_i386_standalone:_no_SKEIN/comment_1_fcf7e1089b25993378df7574ccee8062._comment
new file mode 100644
index 000000000..c725acd62
--- /dev/null
+++ b/doc/bugs/amd64_i386_standalone:_no_SKEIN/comment_1_fcf7e1089b25993378df7574ccee8062._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.43"
+ subject="comment 1"
+ date="2014-01-08T22:06:35Z"
+ content="""
+Those builds are done on Debian stable for portability reasons, and it has too old a version of haskell-cryptohash for SKEIN.
+"""]]
diff --git a/doc/bugs/interference_with_Dropbox_results_in_data_loss/comment_2_fe852adc1d7d3062ace269ceb134f3ad._comment b/doc/bugs/interference_with_Dropbox_results_in_data_loss/comment_2_fe852adc1d7d3062ace269ceb134f3ad._comment
new file mode 100644
index 000000000..475e1dc0a
--- /dev/null
+++ b/doc/bugs/interference_with_Dropbox_results_in_data_loss/comment_2_fe852adc1d7d3062ace269ceb134f3ad._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawkWQXo7MLYIDa-ep04UTbdz8KuvfjwLDCQ"
+ nickname="Matěj"
+ subject="comment 2"
+ date="2014-01-08T22:11:34Z"
+ content="""
+I understand, it's not git-annex fail. I added at least a tip with a warning here: [[tips/do not use git-annex inside your Dropbox]].
+"""]]
diff --git a/doc/tips/do_not_use_git-annex_inside_your_Dropbox.mdwn b/doc/tips/do_not_use_git-annex_inside_your_Dropbox.mdwn
new file mode 100644
index 000000000..266990344
--- /dev/null
+++ b/doc/tips/do_not_use_git-annex_inside_your_Dropbox.mdwn
@@ -0,0 +1,5 @@
+Do not place git-annex enabled git repository inside your Dropbox folder!
+
+You will encounter broken symlinks and git-annex complaining about lost files. Dropbox [doesn't preserve case of file names](https://www.dropbox.com/help/145/en) and this breaks storage of annexed files (.git/annex/objects/). For possible recovery see <http://git-annex.branchable.com/bugs/interference_with_Dropbox_results_in_data_loss>.
+
+
diff --git a/doc/todo/Provide_a___34__git_annex_satisfy__95__num__95__copies__34___command.mdwn b/doc/todo/Provide_a___34__git_annex_satisfy__95__num__95__copies__34___command.mdwn
new file mode 100644
index 000000000..20046785a
--- /dev/null
+++ b/doc/todo/Provide_a___34__git_annex_satisfy__95__num__95__copies__34___command.mdwn
@@ -0,0 +1,9 @@
+Please provide a command that basically performs something like:
+
+git get --auto
+for i in `git remote`; do git copy -to $i --auto; done
+
+
+The use case is this:
+I have a very large repo (300.000 files) in three places. Now I want the fastest possible way to ensure, that every file exists in annex.numcopies. This should scan every file one time and then get it or copy it to other repos as needed. Right now, I make one "git annex get --auto" in every repo, which is is a waste of time, since most of the files never change anyway!
+