{"push_id":1302732311,"size":1,"distinct_size":1,"ref":"refs/heads/stable/boron","head":"6bc40593a886f6b2eaeebbe35d820e0e04a3e6de","before":"4ae63e980a6d95000cef75d368d89c6467a6e767","commits":[{"sha":"6bc40593a886f6b2eaeebbe35d820e0e04a3e6de","author":{"name":"Anil Vishnoi","email":"73e56d390344ad48bf8e8c07976511b89a1de953@gmail.com"},"message":"Updated git submodules\n\nProject: ovsdb stable/boron a57f0a1d359b79795e13ebfa668e5515864d6231\n\nMerge \"Fix clear bug related to \"num\" in JSON Node\" into stable/boron\n\nFix clear bug related to \"num\" in JSON Node\n\nBefore this change, getConstraints() would call populateEnum()  which\nwould ... do nothing, ultimately; this was pointless, as it is currently\nimplemented.\n\nI'm assuming here that the code was meant to do what I turned it into,\nbut I don't understand enough of this code to be certain.  I've also NOT\ntested this in any way.  It does kind of seem reasonable though, looking\nat what the lines before in getConstraints do.\n\nAn alternative would be to just remove those populateEnum methods - if\nthey do nothing, and there is no real bug here, then that was just dead\ncode.  More likely, I suspect it is a real bug that hasn't been found\nyet.\n\nI'll try to add FindBugs error detection for such cases in the future -\nUC_USELESS_OBJECT is exactly for finding these kind of programming\nerrors, AFAIK.\n\nChange-Id: I587e053b5145320b600e2db0109118d799da8822\nSigned-off-by: Michael Vorburger <vorburger@redhat.com>","distinct":true,"url":"https://api.github.com/repos/opendaylight/releng-autorelease/commits/6bc40593a886f6b2eaeebbe35d820e0e04a3e6de"}]}
{"actor":{"display_login":"odl-github"}}