{"push_id":935373948,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"fc9ff95acef27003ad11dbd74fa76fe40ddfb3c0","before":"21563d9cccd0e77af2c236950ddb784721933f05","commits":[{"sha":"3ecdb3b8902b9b612bbe6a41b75086f16f35e97c","author":{"email":"0d1842d94ccb7b6d1b886c2c4096119b4aa7241c@google.com","name":"Nicolas Lacasse"},"message":"jiri: Use the latest update snapshot manifest when computing LocalProjects.\n\nPreviously, when computing LocalProjects with FastPath, we would read\nthe projects from the .jiri_manifest (or manifest specified on the\ncommand line) and check to see if those projects exist on the local\nfilesystem.  If not, we fall back on the slow path of scanning the\nentire filesystem for projects.\n\nThis behavior was incorrect.  In particular, since the .jiri_manifest\nmight have changed since the last update, we would end up scanning the\nfilesystem more often than necessary.\n\nNow, we keep track of the latest update snapshot file with a symlink.\nWhen computing LocalProjects, we read the manifest pointed to by that\nsymlink, which has a much higher probability of matching the projects on\nthe filesystem.  This will cause fewer filesystem scans.\n\nMultiPart: 1/2\nChange-Id: I526f30c8f4605edc02901dd8537e91baefc01807","distinct":true,"url":"https://api.github.com/repos/vanadium/go.jiri/commits/3ecdb3b8902b9b612bbe6a41b75086f16f35e97c"},{"sha":"fc9ff95acef27003ad11dbd74fa76fe40ddfb3c0","author":{"email":"0d1842d94ccb7b6d1b886c2c4096119b4aa7241c@google.com","name":"Nicolas Lacasse"},"message":"Merge \"jiri: Use the latest update snapshot manifest when computing LocalProjects.\"","distinct":true,"url":"https://api.github.com/repos/vanadium/go.jiri/commits/fc9ff95acef27003ad11dbd74fa76fe40ddfb3c0"}]}