summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2014-05-24 14:46:13 -0400
committerGravatar Joey Hess <joey@kitenet.net>2014-05-24 14:46:13 -0400
commit412b1d19917fa1b246dbbcfefc69746e7bcb88d1 (patch)
tree2ba38b360f04f992eecd8119d63056fa20c78499
parent78a33b22a231fae12bb0ce6be590db9817dee844 (diff)
parent9c014fce1dd716041e336e8b2a28259969a1b6be (diff)
Merge branch 'master' of ssh://git-annex.branchable.com
-rw-r--r--doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_6_f28f65901c46d9543797f698b0eedb63._comment8
-rw-r--r--doc/bugs/wget_tarball_over_https_complains/comment_2_25fb35b2e707b174f255a1dafca8eff9._comment10
-rw-r--r--doc/tips/what_to_do_when_a_repository_is_corrupted/comment_2_025178c2b11affe2d42a87544b897dc8._comment8
-rw-r--r--doc/tips/what_to_do_when_a_repository_is_corrupted/comment_3_9a6bae9c0326ecc7610f5415db20f49e._comment8
4 files changed, 34 insertions, 0 deletions
diff --git a/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_6_f28f65901c46d9543797f698b0eedb63._comment b/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_6_f28f65901c46d9543797f698b0eedb63._comment
new file mode 100644
index 000000000..01e386a75
--- /dev/null
+++ b/doc/bugs/Android_version_apparently_unable_to_run_sha256sum/comment_6_f28f65901c46d9543797f698b0eedb63._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.36"
+ subject="comment 6"
+ date="2014-05-23T20:20:05Z"
+ content="""
+I tried to reproduce the assistant behaving that way, but after removing sha256sum from PATH, the assistant failed to add files and complained strenuously.
+"""]]
diff --git a/doc/bugs/wget_tarball_over_https_complains/comment_2_25fb35b2e707b174f255a1dafca8eff9._comment b/doc/bugs/wget_tarball_over_https_complains/comment_2_25fb35b2e707b174f255a1dafca8eff9._comment
new file mode 100644
index 000000000..e2ef20fd8
--- /dev/null
+++ b/doc/bugs/wget_tarball_over_https_complains/comment_2_25fb35b2e707b174f255a1dafca8eff9._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.36"
+ subject="comment 2"
+ date="2014-05-24T17:48:16Z"
+ content="""
+I reproduced this on a debian 6.0 system. Eep that's old. Probably *was* a wget bug.
+
+After downloading with --no-check-certificate, I tried with the wget bundled in the git-annex tarball. That works.
+"""]]
diff --git a/doc/tips/what_to_do_when_a_repository_is_corrupted/comment_2_025178c2b11affe2d42a87544b897dc8._comment b/doc/tips/what_to_do_when_a_repository_is_corrupted/comment_2_025178c2b11affe2d42a87544b897dc8._comment
new file mode 100644
index 000000000..beb177d00
--- /dev/null
+++ b/doc/tips/what_to_do_when_a_repository_is_corrupted/comment_2_025178c2b11affe2d42a87544b897dc8._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawmZilYULa6CDEGfuagoDlesyakBgnf-dF8"
+ nickname="Maarten"
+ subject="comment 2"
+ date="2014-05-23T23:50:58Z"
+ content="""
+What if the drive is destroyed? How would I re-initialize a new drive to act as a substitute for the remote that was just lost?
+"""]]
diff --git a/doc/tips/what_to_do_when_a_repository_is_corrupted/comment_3_9a6bae9c0326ecc7610f5415db20f49e._comment b/doc/tips/what_to_do_when_a_repository_is_corrupted/comment_3_9a6bae9c0326ecc7610f5415db20f49e._comment
new file mode 100644
index 000000000..870d7b93f
--- /dev/null
+++ b/doc/tips/what_to_do_when_a_repository_is_corrupted/comment_3_9a6bae9c0326ecc7610f5415db20f49e._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.36"
+ subject="comment 3"
+ date="2014-05-24T18:29:03Z"
+ content="""
+@Maarten git clone from one of the other clones of the repository to the new drive. Also, recent versions of git-annex have a `git annex reinit` command that can be used to easily initialize a repository with the same settings as a repository that was lost.
+"""]]