[GitHub] ctubbsii commented on issue #295: ACCUMULO-4699 Fixed queued work key in replication

2017-09-05 Thread git
ctubbsii commented on issue #295: ACCUMULO-4699 Fixed queued work key in replication URL: https://github.com/apache/accumulo/pull/295#issuecomment-327306098 What I hear when I hear someone say they were "ignored" is an accusation of active malicious intent on the part of another to

[GitHub] ctubbsii commented on issue #295: ACCUMULO-4699 Fixed queued work key in replication

2017-09-05 Thread git
ctubbsii commented on issue #295: ACCUMULO-4699 Fixed queued work key in replication URL: https://github.com/apache/accumulo/pull/295#issuecomment-327306098 What I hear when I hear someone say they were "ignored" is an accusation of active malicious intent on the part of another to

[GitHub] ctubbsii commented on issue #295: ACCUMULO-4699 Fixed queued work key in replication

2017-09-05 Thread git
ctubbsii commented on issue #295: ACCUMULO-4699 Fixed queued work key in replication URL: https://github.com/apache/accumulo/pull/295#issuecomment-327289076 @joshelser I was attempting to gently remind you to "assume good intentions", as stated in the ASF Code of Conduct, enforcement of

[GitHub] ctubbsii commented on issue #295: ACCUMULO-4699 Fixed queued work key in replication

2017-09-05 Thread git
ctubbsii commented on issue #295: ACCUMULO-4699 Fixed queued work key in replication URL: https://github.com/apache/accumulo/pull/295#issuecomment-327275588 Careful not to assume a comment is ignored, versus other options, such as "thought I already responded", "overlooked/missed", "still