From d604be587898c015282ac65a40c6e1714c4870e5 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Thu, 22 Feb 2018 17:18:18 +0000 Subject: Added a comment: --read-only flag? --- .../comment_2_066d2f95ffab1b36b69aa84643d67765._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/impossible_to_perform___34__read-only__34___git_annex_info_without_write_permissions/comment_2_066d2f95ffab1b36b69aa84643d67765._comment diff --git a/doc/bugs/impossible_to_perform___34__read-only__34___git_annex_info_without_write_permissions/comment_2_066d2f95ffab1b36b69aa84643d67765._comment b/doc/bugs/impossible_to_perform___34__read-only__34___git_annex_info_without_write_permissions/comment_2_066d2f95ffab1b36b69aa84643d67765._comment new file mode 100644 index 000000000..0863efa27 --- /dev/null +++ b/doc/bugs/impossible_to_perform___34__read-only__34___git_annex_info_without_write_permissions/comment_2_066d2f95ffab1b36b69aa84643d67765._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="--read-only flag?" + date="2018-02-22T17:18:18Z" + content=""" +I hear you... so far though I was confused by the fact that what I thought would be a read-only operation was actually changing the state of the things (doing the annex merge). Although I would have preferred just a warning like \"Cannot merge git-annex branch because of lacking permissions to do so, some information might be not up-to-date\", I wondered if then may be a generic resolution could be to add `--read-only` flag to such commands as `info` and `whereis`. Then we (datalad) would be the one to explicitly check if there is write-permissions and if not -- issue the command in `--read-only` mode. We might even make it a default mode of operation for some of our usecases where it would be confusing if things were changing in the background (e.g. with `ls` command) +"""]] -- cgit v1.2.3