Clone this repo:
  1. 7f37955 Generated files from "codesearch-gen-chromium-android" build 1919, revision 66c8550045d1ca168b36b33d821154143b6b4c54 by Automatic Generated Files Sync · 4 hours ago master
  2. 016b66f Generated files from "codesearch-gen-chromium-linux" build 3020, revision 66c8550045d1ca168b36b33d821154143b6b4c54 by Automatic Generated Files Sync · 4 hours ago
  3. 693412b Generated files from "codesearch-gen-chromium-linux" build 3019, revision 8628464d9d66de109c49cb517f158a432cb8079f by Automatic Generated Files Sync · 9 hours ago
  4. 5956a81 Generated files from "codesearch-gen-chromium-android" build 1918, revision 8628464d9d66de109c49cb517f158a432cb8079f by Automatic Generated Files Sync · 9 hours ago
  5. 81793cf Generated files from "codesearch-gen-chromium-android" build 1917, revision 12ed67d3c95b9239a3d580f5437c203ad3dd56f6 by Automatic Generated Files Sync · 13 hours ago

What's this?

This git repository exists to allow the source files generated during a Chromium build to be indexed by code search (https://cs.chromium.org).

You do not need to clone this repository, and it is not used in any way during a build.

How does it work?

A build slave regularly does a full Linux build of Chromium, and afterwards pushes all the generated files (from the src/out/Debug/gen directory) into this git repository.

Another build slave maintains a git repository containing gitlinks (git submodules) representing the dependencies specified in Chromium's DEPS file. That script also adds a gitlink named “out” pointing to this repository.

The code search crawler indexes that gitlink repository following all the gitlinks inside, which eventually leads it here and allows it to index the generated code.