Merge branch 'master' of ssh://git-annex.branchable.com

4 files changed, 54 insertions, 0 deletions

diff --git a/doc/bugs/403_for_windows_installer_download.mdwn b/doc/bugs/403_for_windows_installer_download.mdwn
new file mode 100644
index 000000000..e5426f087
--- /dev/null
+++ b/doc/bugs/403_for_windows_installer_download.mdwn
@@ -0,0 +1,23 @@
+### Please describe the problem.
+As of Nov 2, 2016 1:30AM EST, no Windows installer is to be found in https://downloads.kitenet.net/git-annex/windows/current/. Accessing .exe URI directly yields a 403 error. Not sure if this is a temporary hiccup or a script error somewhere -- pardon if this is not the right channel to report this issue.
+
+### What steps will reproduce the problem?
+See https://downloads.kitenet.net/git-annex/windows/current/.
+
+### What version of git-annex are you using? On what operating system?
+N/A
+
+### Please provide any additional information below.
+N/A
+
+[[!format sh """
+# If you can, paste a complete transcript of the problem occurring here.
+# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
+
+
+# End of transcript or log.
+"""]]
+
+### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
+Yes! Worked like a charm on my Mac.
+
diff --git a/doc/bugs/addurl_pathdepth_description_misleading.mdwn b/doc/bugs/addurl_pathdepth_description_misleading.mdwn
new file mode 100644
index 000000000..531e43cbf
--- /dev/null
+++ b/doc/bugs/addurl_pathdepth_description_misleading.mdwn
@@ -0,0 +1,13 @@
+The description for the *pathdepth* option for *addurl* doesn't match its behaviour (emphasis mine).
+
+> Rather than basing the **filename** on the whole url, this causes a **path** to be constructed, starting at the specified depth within the path of the url.
+> 
+> For example, adding the url http://www.example.com/dir/subdir/bigfile with --pathdepth=1 will use "**dir/subdir/bigfile**", while --pathdepth=3 will use "bigfile".
+
+This isn't how it behaves. It would be more accurate as (emphasis on changes):
+
+> Rather than basing the filename on the whole url, this causes a **filename** to be constructed, starting at the specified depth within the path of the url.
+> 
+> For example, adding the url http://www.example.com/dir/subdir/bigfile with --pathdepth=1 will use "**dir_subdir_bigfile**", while --pathdepth=3 will use "bigfile".
+
+For what I am doing (adding a directory tree with addurl and file:// URLs), I'd actually like the behaviour described (to recreate the tree), but I'm not sure which one was the *intended* behaviour..
diff --git a/doc/bugs/addurl_pathdepth_description_misleading/comment_1_e4e0a6e27ba5d7d95468e017ec07fa77._comment b/doc/bugs/addurl_pathdepth_description_misleading/comment_1_e4e0a6e27ba5d7d95468e017ec07fa77._comment
new file mode 100644
index 000000000..59a62f387
--- /dev/null
+++ b/doc/bugs/addurl_pathdepth_description_misleading/comment_1_e4e0a6e27ba5d7d95468e017ec07fa77._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="CandyAngel"
+ avatar="http://cdn.libravatar.org/avatar/15c0aade8bec5bf004f939dd73cf9ed8"
+ subject="comment 1"
+ date="2016-11-02T10:03:46Z"
+ content="""
+Sorry, you can ignore this for now. I just noticed I'm using 6.20160613.. the Arch Linux version (in community) is really out of date.
+
+I'll update and confirm if this is actually an issue.
+"""]]
diff --git a/doc/bugs/addurl_pathdepth_description_misleading/comment_2_888bc4ffd264fbd8d07f07c017dec278._comment b/doc/bugs/addurl_pathdepth_description_misleading/comment_2_888bc4ffd264fbd8d07f07c017dec278._comment
new file mode 100644
index 000000000..1c37fb29e
--- /dev/null
+++ b/doc/bugs/addurl_pathdepth_description_misleading/comment_2_888bc4ffd264fbd8d07f07c017dec278._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="CandyAngel"
+ avatar="http://cdn.libravatar.org/avatar/15c0aade8bec5bf004f939dd73cf9ed8"
+ subject="comment 2"
+ date="2016-11-02T10:37:48Z"
+ content="""
+Tested on 6.20161102-g330c68b and the description/behaviour mismatch still exists.
+"""]]