Added a comment
This commit is contained in:
parent
cc62ba1da8
commit
9f00137022
1 changed files with 19 additions and 0 deletions
|
@ -0,0 +1,19 @@
|
|||
[[!comment format=mdwn
|
||||
username="strmd"
|
||||
avatar="http://cdn.libravatar.org/avatar/035707b9756129bbdea6b36a7f7b38d3"
|
||||
subject="comment 33"
|
||||
date="2019-10-29T20:01:01Z"
|
||||
content="""
|
||||
@joey,
|
||||
|
||||
Thanks for your reply. I certainly appreciate you giving your perspective and rationale, and you bring up several good points. I never intended for my comment to be hostile or harsh, and I'm sorry if it struck you that way.
|
||||
|
||||
I do believe you acted in the best of intentions, and going back through the devblog and documentation one can follow along and see how this change came about. So the bit about it being casually communicated, as I wrote, is in one sense absolutely false.
|
||||
|
||||
And yet, to me, a somewhat recent user (who still find aspects of git-annex and its inner workings hard to grasp at times), it appeared to happen without warning and came pretty much out of nowhere. As you note, there are several reasons for that, and I'm obviously responsible for making sure I understand the tools I use.
|
||||
|
||||
As you have touched upon on your personal blog, there are probably some lessons to learn here. I hope we can turn it into something constructive. And mostly, I hope we as a community can avoid putting you in this regrettable position again.
|
||||
|
||||
Finally, the solution you have come up with since my post, seems very, very good and should alleviate most, if not all, concerns.
|
||||
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue