diff --git a/doc/bugs/GETURLS_doesn__39__t_return_URLs_if_prefix_is_provided/comment_2_a0c3c27ff70b98a83f77ebac2714f8c7._comment b/doc/bugs/GETURLS_doesn__39__t_return_URLs_if_prefix_is_provided/comment_2_a0c3c27ff70b98a83f77ebac2714f8c7._comment
new file mode 100644
index 0000000000..26815a6a5e
--- /dev/null
+++ b/doc/bugs/GETURLS_doesn__39__t_return_URLs_if_prefix_is_provided/comment_2_a0c3c27ff70b98a83f77ebac2714f8c7._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawnx8kHW66N3BqmkVpgtXDlYMvr8TJ5VvfY"
+ nickname="Yaroslav"
+ subject="comment 2"
+ date="2015-03-27T20:04:23Z"
+ content="""
+could you try on your end with as obscure URL as mine? i.e.
+'dl+archive:SHA256E-s153--f378a42b6ff4d90091a7dfa37ebe1fe2fc5926eafd12cde1f2ba5fd1bcbf5e1e.tar.gz/d/test.dat'
+may be something to do with the / in the url name?
+as posted on IRC, here are  two runs protocols with all the details, where I don't spot any related difference in runs
+http://www.onerussian.com/tmp/run-bad.txt_   http://www.onerussian.com/tmp/run-good.txt_
+"""]]
diff --git a/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load/comment_2_dbc07ece175d747126ae626cd45ffb49._comment b/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load/comment_2_dbc07ece175d747126ae626cd45ffb49._comment
new file mode 100644
index 0000000000..dd8cad0812
--- /dev/null
+++ b/doc/bugs/for_custom_remotes_provide_enhanced_DIRHASH_which_outputs_full_DIRHASH_to_the_key_load/comment_2_dbc07ece175d747126ae626cd45ffb49._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawnx8kHW66N3BqmkVpgtXDlYMvr8TJ5VvfY"
+ nickname="Yaroslav"
+ subject="you read my mind correctly"
+ date="2015-03-27T19:43:01Z"
+ content="""
+Indeed I was just trying to get to the key's content (i.e. original archive from which to extract the load).  Indeed, new command would be lovely to have 
+
+I started to wonder what would be faster though -- calling another git annex instance with that command or asking through the PIPE/interface?
+
+P.S. I am scared to try any real tarball usecase and see how well it scales or not with all the ping-pong between external remote and annex ;)  I guess I will discover soon
+"""]]