| commit | f0110db95bc9eeb6bea7dbdd5696d1c591821c06 | [log] [tgz] |
|---|---|---|
| author | bnc <bnc@google.com> | Thu May 12 13:50:22 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu May 12 13:51:07 2022 -0700 |
| tree | 4dcda343e7d78378fc929b969acc262e13bb254e | |
| parent | f2c580bf0c4a0bf9d886c6e571b25e19b275a6c3 [diff] |
Move some QUICHE presubmit checks from individual files to METADATA.common. Also add "check_delta_only: false" to make sure entire files are scanned. I verified that all existing files comply (or added the non-compliant ones as exclusions). Of the new path exclusions, the ones I intend to fix immediately I marked with a TODO with my name. One that is pending a flag deprecation is marked with a TODO and a bug number. The rest I do not intend to fix, but moving them to METADATA.common so that they apply to all new code, not only a proper subset, is an improvement anyway. PiperOrigin-RevId: 448330048
QUICHE stands for QUIC, Http, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.
There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:
To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:
To contribute to QUICHE, follow instructions at CONTRIBUTING.md.
QUICHE is only supported on little-endian platforms.