| commit | afba1ee7ecdcfae7e93337e2d955d580b0a48f31 | [log] [tgz] |
|---|---|---|
| author | Hidehiko Abe <hidehiko@chromium.org> | Tue Jul 28 09:47:45 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Jul 28 09:47:45 2020 +0000 |
| tree | 5b0d6a9d03276d7953987f14019ff6fdd4e4c117 | |
| parent | 4b4f0480d0c0bebcc38e88e5d6d12cf92bdc8aaf [diff] | |
| parent | 6de1ded66aa00a4cc29d750f115dbd42beefbb3f [diff] |
Update OWNERS to reflect current situation. am: 6de1ded66a Original change: https://android-review.googlesource.com/c/platform/external/libbrillo/+/1373140 Change-Id: Ia53539945ea812d1d0c82ee2416a7aa749a397c3
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.