From c3e0856b4556e7b2076294431b2a64f09f47cc12 Mon Sep 17 00:00:00 2001 From: kyle Date: Fri, 11 Dec 2020 20:56:04 +0000 Subject: [PATCH] Added a comment --- ..._2_fcdc6ef1dd464d25ec3e26dac828830e._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/bugs/windows__58___commits_created_despite_alwayscommit__61__fals/comment_2_fcdc6ef1dd464d25ec3e26dac828830e._comment diff --git a/doc/bugs/windows__58___commits_created_despite_alwayscommit__61__fals/comment_2_fcdc6ef1dd464d25ec3e26dac828830e._comment b/doc/bugs/windows__58___commits_created_despite_alwayscommit__61__fals/comment_2_fcdc6ef1dd464d25ec3e26dac828830e._comment new file mode 100644 index 0000000000..dcdf47855f --- /dev/null +++ b/doc/bugs/windows__58___commits_created_despite_alwayscommit__61__fals/comment_2_fcdc6ef1dd464d25ec3e26dac828830e._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="kyle" + avatar="http://cdn.libravatar.org/avatar/7d6e85cde1422ad60607c87fa87c63f3" + subject="comment 2" + date="2020-12-11T20:56:04Z" + content=""" +Thanks for response. + +> However, the other thing is that \"alwayscommit=false\" does not +> really imply \"never commit in any circumstances\". [...] I don't know +> if I would consider that a bug. + +Fair point. At least for the spots I'm aware of, DataLad's use of +alwayscommit=false aligns fine with that. We're performing operations +where we'd _like_ to reduce the number of commits, but that being +effective is in no way relied on. +"""]]