diff --git a/doc/bugs/warning_about_ssh_caching_keeps_showing/comment_2_43b651b09b91986d5cb4ae14c83017c7._comment b/doc/bugs/warning_about_ssh_caching_keeps_showing/comment_2_43b651b09b91986d5cb4ae14c83017c7._comment new file mode 100644 index 0000000000..c2335f2b14 --- /dev/null +++ b/doc/bugs/warning_about_ssh_caching_keeps_showing/comment_2_43b651b09b91986d5cb4ae14c83017c7._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="ssh caching" + date="2020-02-14T20:53:27Z" + content=""" +\"your build of git-annex may have been made without ssh connection caching support, which would happen if its configure program detected at build time that ssh doesn't support it\" -- yes, according to the [build log](https://dev.azure.com/conda-forge/84710dde-1620-425b-80d0-4cf5baca359d/_apis/build/builds/117561/logs/8). I can add an ssh dependency to the conda-forge git-annex recipe. It would be more flexible to not have that dependency and instead to have git-annex's behavior depend on the ssh available at runtime; but, I guess there's a reason it's a compile-time option? + +Also, I don't have ssh prompting for passwords since I use ssh-agent, and having the warning shown every time is distracting. Maybe, a config option could be added to disable the warning? +"""]] diff --git a/doc/bugs/warning_about_ssh_caching_keeps_showing/comment_3_49182db51bd86f0c60fadde5e4643f77._comment b/doc/bugs/warning_about_ssh_caching_keeps_showing/comment_3_49182db51bd86f0c60fadde5e4643f77._comment new file mode 100644 index 0000000000..0b8e66f301 --- /dev/null +++ b/doc/bugs/warning_about_ssh_caching_keeps_showing/comment_3_49182db51bd86f0c60fadde5e4643f77._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 3" + date="2020-02-15T04:45:01Z" + content=""" +Ilya, you wrote \"the ability to easily write your own external **backends** has been especially helpful\". Did you mean \"external **remotes**\"? since \"external backends\" are yet [TODO AFAIK](https://git-annex.branchable.com/todo/external_backends/) +"""]] diff --git a/doc/bugs/warning_about_ssh_caching_keeps_showing/comment_4_ab823204f02dd26ebfe0613f711e0f9d._comment b/doc/bugs/warning_about_ssh_caching_keeps_showing/comment_4_ab823204f02dd26ebfe0613f711e0f9d._comment new file mode 100644 index 0000000000..9a029fefbf --- /dev/null +++ b/doc/bugs/warning_about_ssh_caching_keeps_showing/comment_4_ab823204f02dd26ebfe0613f711e0f9d._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="comment 4" + date="2020-02-16T04:05:11Z" + content=""" +Yes, I meant external remotes. +"""]] diff --git a/doc/special_remotes/comment_40_2a36f9c874b00fd5de94836e3dcde782._comment b/doc/special_remotes/comment_40_2a36f9c874b00fd5de94836e3dcde782._comment new file mode 100644 index 0000000000..9f71e141fc --- /dev/null +++ b/doc/special_remotes/comment_40_2a36f9c874b00fd5de94836e3dcde782._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="giuly.ippoliti@c1e2f0d5e40b128900f94f3d107d3719f87c3ff7" + nickname="giuly.ippoliti" + avatar="http://cdn.libravatar.org/avatar/4444ce1930af68fd817e9649d40e0359" + subject="Disable git annex logs" + date="2020-02-14T19:39:26Z" + content=""" +Hi, + +So while writing the globus special remote (git-annex-remote-globus) I often redirect my logs to annex. Nevertheless these logs are always logged out in the console, them being INFO, ERROR, DEBUG and I would like to control that. Is there a way to disable console logging of logs sent back to git annex? + +Something like ANNEX_LOG_LEVEL=self.annex.ERROR + +Thanks !! + +Regards +Giulia +"""]]