Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / fcbd0ba75fc88c49755703bc5ed71d06a2b52c2a
commitfcbd0ba75fc88c49755703bc5ed71d06a2b52c2a[log] [tgz]
authorRoberto Gil Del Sol <robertogil@google.com>Fri Mar 17 11:05:33 2023 +0000
committerRoberto Gil Del Sol <robertogil@google.com>Fri Mar 17 11:05:38 2023 +0000
tree082961c9e83646ea493477a196f06e213660ab2b
parentdc4a110e2f336ac654daa97d2dea667e69c0e392 [diff]
Remove satayev from OWNERS

Bug: 274075231
Change-Id: I1ebb623d740916a2919f2e96b446745896aeb983
4 files changed
tree: 082961c9e83646ea493477a196f06e213660ab2b
  1. build/
  2. java/
  3. javatests/
  4. proguard/
  5. proto/
  6. sdk/
  7. tools/
  8. Android.bp
  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.