Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / ac02c035d0c7b3e06552634dd5a37df88c1fe66e
commitac02c035d0c7b3e06552634dd5a37df88c1fe66e[log] [tgz]
authorPedro Loureiro <pedroql@google.com>Wed Jul 05 14:10:35 2023 +0000
committerPedro Loureiro <pedroql@google.com>Wed Jul 05 14:28:44 2023 +0000
tree2c7832175c822f9a2ae9ec5eaeaef4d33cf3cee1
parent9420ecb9b68350b716b2cba345c67e80ff6a4cbb [diff]
Update owners

Add (not so) new members of the team to the OWNERS file.

Test: N/A
Change-Id: If4802761f5dec9c6f21c43d26ee5c0292654d96a
1 file changed
tree: 2c7832175c822f9a2ae9ec5eaeaef4d33cf3cee1
  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.