| commit | f3d0d1c32b222899b5fd7980d0f5b41e27354a1a | [log] [tgz] |
|---|---|---|
| author | [email protected] <[email protected]@0039d316-1c4b-4281-b951-d872f2087c98> | Thu May 22 22:12:48 2014 |
| committer | [email protected] <[email protected]@0039d316-1c4b-4281-b951-d872f2087c98> | Thu May 22 22:12:48 2014 |
| tree | 8b66bdb086f122e82395ebbe7c1f1d5d94b9893f | |
| parent | 3b84344b82f0e3ddfa8cb2cb6b7c95dff27c87dd [diff] |
Always write .landmines Otherwise, if .landmines exists, and isn't clobbered by the clobber in compile.py, every build will cause a clobber until .landmines is removed. Trying to fix http://crbug.com/375459 brought this up. In that case compile.py wasn't removing .landmines, which is necessary in the case of a landmines change on two subsequent builds. If .landmines isn't maintained, then there's nothing to diff against on the second build and so a clobber won't be correctly triggered. [email protected],[email protected] BUG=376359 Review URL: https://codereview.chromium.org/293983017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@272341 0039d316-1c4b-4281-b951-d872f2087c98