Clone this repo:
  1. bb3ab6d Generated files from "codesearch-gen-chromium-linux" build 835, revision 86716087cc70f251aad2111ec6d86711239c44ab by Automatic Generated Files Sync · 4 hours ago master
  2. b7c215b Generated files from "codesearch-gen-chromium-linux" build 834, revision 2fbcfb5397651fdf4f680cb1e37ca8e38bfd6bd9 by Automatic Generated Files Sync · 8 hours ago
  3. d5cce6f Generated files from "codesearch-gen-chromium-linux" build 833, revision cbf7050ee81b7ca0390e634cfd08f764f33f1307 by Automatic Generated Files Sync · 12 hours ago
  4. 800292b Generated files from "codesearch-gen-chromium-linux" build 832, revision ce88977522c4fe591533766756a41c83d9225d32 by Automatic Generated Files Sync · 16 hours ago
  5. fe42112 Generated files from "codesearch-gen-chromium-linux" build 831, revision b87aed4000a7e2824a8146891cc733bba653879c by Automatic Generated Files Sync · 20 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.