{"push_id":843897887,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"d1f0e7273401e1470b8ed919961e6989eab1f986","before":"9b3bda923212261e95c87042f9ec2b0728aa0e6f","commits":[{"sha":"d1f0e7273401e1470b8ed919961e6989eab1f986","author":{"email":"2adbecb1eb75cc4b145f05fedca73a3c053b9a41@br-automation.com","name":"Roland Knall"},"message":"frame_data: Reset subnum if visited is resetted\n\n subnum get's resetted when the file is reloaded. But subnum\n does not get resetted, if for instance a preference has been\n set directly via (Protocol Name)->Protocol Preferences-> ...\n in the Protocol list. But flags.visited get's resetted.\n\n This leads to the scenario, where reloading a trace starts subnum\n with 0 and applying a preference starts subnum with the highest\n value it had before.\n\n This patch ensures, that all methods for reloading the frame\n lead to the same init value\n\nChange-Id: I167d1e03f7e2e6c60492f501ee5cb9555ac12ac9\nReviewed-on: https://code.wireshark.org/review/11341\nReviewed-by: Roland Knall <rknall@gmail.com>\nReviewed-by: Michael Mann <mmann78@netscape.net>\nReviewed-by: Pascal Quantin <pascal.quantin@gmail.com>","distinct":true,"url":"https://api.github.com/repos/wireshark/wireshark/commits/d1f0e7273401e1470b8ed919961e6989eab1f986"}]}