| commit | 1bc90b6342c6fc1eee06ca952b3923ec3ec1d188 | [log] [tgz] |
|---|---|---|
| author | Hidehiko Abe <hidehiko@chromium.org> | Tue Jul 28 10:28:21 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Jul 28 10:28:21 2020 +0000 |
| tree | 5b0d6a9d03276d7953987f14019ff6fdd4e4c117 | |
| parent | d4bf0e9fd29413d3d07b98da2811a4f6b8efd97b [diff] | |
| parent | 2d11cdd2de14c1ced2416a2b642b1c15468e4279 [diff] |
Update OWNERS to reflect current situation. am: 6de1ded66a am: afba1ee7ec am: 2d11cdd2de Original change: https://android-review.googlesource.com/c/platform/external/libbrillo/+/1373140 Change-Id: I2a905d36008e8ae164a08a173de22ff0b40d4dcd
libbrillo is a shared library meant to hold common utility code that we deem useful for platform projects. It supplements the functionality provided by libbase/libchrome since that project, by design, only holds functionality that Chromium (the browser) needs. As a result, this tends to be more OS-centric code.
This project is also used by Update Engine which is maintained in AOSP. However, AOSP doesn't use this codebase directly, it maintains its own libbrillo fork.
To help keep the projects in sync, we have a gsubtree set up on our GoB: https://chromium.googlesource.com/chromiumos/platform2/libbrillo/
This allows AOSP to cherry pick or merge changes directly back into their fork.