{"push_id":1362062417,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"a6d81effbc23acce59fd88b8f828fe8c753eeb0d","before":"7f6a4926d2f6a135960146041c29802db616aa63","commits":[{"sha":"a6d81effbc23acce59fd88b8f828fe8c753eeb0d","author":{"name":"Guy Harris","email":"797b6f4d9d75383359da362ebbb69879a87cae81@alum.mit.edu"},"message":"Clean up file handle management.\n\nThe main reason fclose() could fail is if the file is open for writing,\nnot all the buffered data has been written out at the time fclose() was\ncalled, and the attempt to write it out fails.  In any case, the file\nhandle is no longer valid after fclose() completes, whether the close\nsucceeds or not, so there's no reason to keep it around.\n\nThere's no reason to check whether it's null in a loop called in code\nwhere it's not null to start with and where it's not set to null in the\nloop.\n\nThis should fix CID 1374111.\n\nChange-Id: Ib8067a17731b41d6b184a5a415addc2ecaa7c00c\nReviewed-on: https://code.wireshark.org/review/18359\nReviewed-by: Guy Harris <guy@alum.mit.edu>","distinct":true,"url":"https://api.github.com/repos/wireshark/wireshark/commits/a6d81effbc23acce59fd88b8f828fe8c753eeb0d"}]}
{"actor":{"display_login":"wireshark-gerrit"}}