{"push_id":707548198,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"b48f72a833ab93e9f74f7e788f8451116e1a4bb3","before":"f3c5cef186e13548e077768c8ec219a65a753700","commits":[{"sha":"b48f72a833ab93e9f74f7e788f8451116e1a4bb3","author":{"email":"68841e62bd2061843a4f4a0261e80b673d56389c@google.com","name":"Aaron Jacobs"},"message":"Assign new generation numbers when copying in gcsfake.\n\nThis upholds the real GCS guarantee that the generation number for a\nparticular name cannot regress. This was coming up in a gcsfuse\nintegration that did the following:\n\n1.  Create 'foo'.\n2.  Create 'bar'.\n3.  Rename 'foo' on top of 'bar'.\n\nThis resulted in the generation number for 'bar' going backwards, which\nviolated a file system assumption and caused the inode lookup loop to\nnot converge.\n\nFor GoogleCloudPlatform/gcsfuse#81.","distinct":true,"url":"https://api.github.com/repos/jacobsa/gcloud/commits/b48f72a833ab93e9f74f7e788f8451116e1a4bb3"}]}