Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / f144f37289117cd09a5ce474cedf0176fd40cd65
commitf144f37289117cd09a5ce474cedf0176fd40cd65[log] [tgz]
authorMatthew Maurer <mmaurer@google.com>Mon Oct 25 13:37:17 2021 -0700
committerMatthew Maurer <mmaurer@google.com>Tue Oct 26 18:25:17 2021 -0700
tree4a24dbc60e51dfe535a01edfd93c9cfc9a5eb609
parent0e2804463f8f6e2396c259d221e993e60d791725 [diff]
Allow thiserror for use in DoH

This is a macro+instance-only crate, so it adds no weight by itself.

Test: DoH throughput test
Apex-Size-Increase: 0k
Previous-Platform-Support: No platform dependencies
Aosp-First: AOSP-first
Test-Info: Unit tests run in TEST_MAPPING on project updates
Bug: 202081046

Change-Id: Id558a6729814bf4d0229dd53a4cf277b887a9e31
1 file changed
tree: 4a24dbc60e51dfe535a01edfd93c9cfc9a5eb609
  1. build/
  2. java/
  3. proguard/
  4. proto/
  5. sdk/
  6. tools/
  7. Android.bp
  8. generate_ml_bundle.sh
  9. MODULES_OWNERS
  10. OWNERS
  11. PREBUILTS_MODULE_OWNERS
  12. PREUPLOAD.cfg
  13. README.md
README.md

packages/modules/common

This project includes mainline build and other utility code. Any library code intended for use by modules should go in frameworks/libs/modules-utils instead.

java code

This project uses a single source path for java code. All java code should go in the java directory with subdirectories corresponding to the java package. Android.bp files should go alongside the java source files, and should only include java source for a single java package to encourage good code hygiene.

Tests for java code should go in the javatests directory and follow the same structure.