forked from chromium/chromium
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use the authoritative upstream source for Breakpad, move to third_party
Breakpad was being synced from a read-only mirror of a subdirectory rather than the authoritative upstream source. This encouraged Chrome developers to send patches against the read-only mirror. Those patches couldn’t be committed and needed to be duplicated in the correct repository. Once, a patch against the read-only mirror accidentally was committed, and it broke mirroring. This odd setup existed from the time of the git migration. Prior to that, Breakpad was hosted in Subversion, and Chrome incidentally pulled Breakpad’s src subdirectory rather than the entire trunk directory. Because it wasn‘t easy to do the same thing with git, the read-only mirror of src was created to avoid having to change lots of paths in Chrome. But now I’m changing the paths. This also moves Breakpad from the top-level breakpad directory in Chrome to third_party/breakpad. It should have been there all along, but Breakpad was one of the earliest dependencies added to Chrome, and at that time, there was no firm policy on where to put Google-originated external code. Bug: 766917 TBR: pinkerton@chromium.org Change-Id: I860a3e92b0327898ba73b8678af258a9020eeaaf Reviewed-on: https://chromium-review.googlesource.com/677280 Commit-Queue: Mark Mentovai <mark@chromium.org> Reviewed-by: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#503925}
- Loading branch information
1 parent
a2aa7d8
commit 5b41612
Showing
80 changed files
with
1,169 additions
and
1,162 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.