| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | sepolicy: Put theme service in its own context | d34d | 2016-08-02 | 1 | -0/+7 |
| | | | | | | | | Allow the theme manager and its data to be sandboxed in its own context Change-Id: I7898663d1c196bfe04fa4c539d20191a43fde284 | ||||
| * | sepolicy: Allow CMUpdater/uncrypt access to recovery_cache_file | dhacker29 | 2015-02-21 | 1 | -0/+7 |
| | | | | | Change-Id: I514d128160ed4e04564077d7a2e2ad297af92e28 | ||||
| * | sepolicy: Start CM Common sepolicy | William Roberts | 2013-08-17 | 1 | -0/+17 |
| Rather than having to maintain out of tree changes, it is often easier to maintain a hiearchy of changes, starting with the vendors common config file. From there, inheriting products can pick up a base and start to add or remove certain bits from it, making use of the BOARD_SEPOLICY_* functions documented in external/sepolicy/README. Change-Id: I28a4aaf6c126535f0a88001582641b234a750015 | |||||
 |
index : vendor_replicant.git | |
| vendor/replicant | git repository hosting |
| summaryrefslogtreecommitdiffstats |