Github user spmallette commented on the issue:
    I assume #427 doesn't need 120cef6 ?  I don't think the dual merge commits 
hurt anything from the git history perspective.  I assume that you merged in 
TINKERPOP-927, realized you needed something else in TINKERPOP-927, committed 
again in there and then had to merge again to TINKERPOP-927-master? If so you 
could have `git reset --hard origin/master` on the TINKERPOP-927-master branch 
and then just remerged TINKERPOP-927 into it which would have given you one 
merge commit.
    This is an awesome and important PR by the way - can't wait to start using 

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

Reply via email to