summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa.mdwn20
-rw-r--r--doc/bugs/error_when_using_repositories_with_non-ASCII_characters/comment_1_38cc2d2ed907649df085de8ad83cb9dd._comment14
-rw-r--r--doc/forum/special_remote_for_iPods.mdwn5
3 files changed, 39 insertions, 0 deletions
diff --git a/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa.mdwn b/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa.mdwn
new file mode 100644
index 000000000..71b8d9117
--- /dev/null
+++ b/doc/bugs/bad_comment_in_ssh_public_key_ssh-rsa.mdwn
@@ -0,0 +1,20 @@
+What steps will reproduce the problem?
+I was trying to pair two repositories on 2 different computers,
+but my public key had this email address at the end:
+bachir@Bachirs-iMac.local
+
+What is the expected output? What do you see instead?
+I was expecting successful pairing.
+I got:
+bad comment in ssh public key ssh-rsa
+AAB3....SAK
+bachir@Bachirs-iMac.local
+
+What version of git-annex are you using? On what operating system?
+I am using the package git-annex Version: 3.20120925
+on MacOSX Lion
+
+Please provide any additional information below.
+I've checked your code, seems to complain about the dash '-' in the email address
+bachir@Bachirs-iMac.local
+
diff --git a/doc/bugs/error_when_using_repositories_with_non-ASCII_characters/comment_1_38cc2d2ed907649df085de8ad83cb9dd._comment b/doc/bugs/error_when_using_repositories_with_non-ASCII_characters/comment_1_38cc2d2ed907649df085de8ad83cb9dd._comment
new file mode 100644
index 000000000..69d7f1da1
--- /dev/null
+++ b/doc/bugs/error_when_using_repositories_with_non-ASCII_characters/comment_1_38cc2d2ed907649df085de8ad83cb9dd._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawmcYryijvlF8bJvM_eZNSrUPEkMlxMDGTQ"
+ nickname="Thiago"
+ subject="The bug is actually something completely different!"
+ date="2012-10-04T03:53:57Z"
+ content="""
+Ok, this is a mix of luser error and a bug.
+
+I noticed that I wasn't providing a description in git annex init. So if I do \"git annex init foo\" in the first repository and \"git annex init bar\" in the clone, then git annex status works!
+
+So the bug is actually that you need to provide a description in git annex init, even though the man page says a description will be generated otherwise.
+
+(In my defense I hit the non-ACII characters bug with the git annex version in Ubuntu, and that one still has the same error even if a description is provided so this was fixed later).
+"""]]
diff --git a/doc/forum/special_remote_for_iPods.mdwn b/doc/forum/special_remote_for_iPods.mdwn
new file mode 100644
index 000000000..eddda5936
--- /dev/null
+++ b/doc/forum/special_remote_for_iPods.mdwn
@@ -0,0 +1,5 @@
+I know versions of this question have been asked before, but I'm looking for a different answer.
+
+I would like a braindead special remote that can be used with devices such as portable music players. No symbolic links, no hashing, no rewriting of the filenames. The remote can be untrusted, file identity can be checked with just the filename and maybe the size. The "directory" special remote with the WORM backend seems to come closest, but does too much.
+
+Should I just try to roll it using hooks?