4e2aaabd13
* Instead of having to enumerate packages and do a bunch of tedious shit, we now have a way to do it automatically based only on the blob lists. * Devices still need to implement a short script, but this library handles all the core functions. * Yes, we should probably be doing this in Python- Bash is absolutely horrible at dealing with arrays and lists. Change-Id: I73b30ff4531c4d1b33ac53db33abf62555f500b4 |
||
|---|---|---|
| ambientsdk | ||
| bash_completion | ||
| build | ||
| config | ||
| gello | ||
| overlay | ||
| prebuilt/common | ||
| sepolicy | ||
| .gitignore | ||
| CHANGELOG.mkdn | ||
| CONTRIBUTORS.mkdn | ||
| LICENSE | ||
| README.mkdn | ||
| vendorsetup.sh | ||
README.mkdn
CyanogenMod
Submitting Patches
Patches are always welcome! Please submit your patches via CyanogenMod Gerrit! You can do this by using these commands:
(From root android directory)
. build/envsetup.sh
(Go to repo you are patching, make your changes and commit)
cmgerrit <for(new)/changes(patch set)> <branch/change-id>
repo start cm-13.0 .
(Make your changes and commit)
repo upload .
Note: "." meaning current directory For more help on using this tool, use this command: repo help upload
Make your changes and commit with a detailed message, starting with what you are working with (i.e. vision: Update Kernel) Commit your patches in a single commit. Squash multiple commit using this command: git rebase -i HEAD~<# of commits>
To view the status of your and others' patches, visit CyanogenMod Code Review
Getting Started
To get started with Android/CyanogenMod, you'll need to get familiar with Repo and Version Control with Git.
To initialize your local repository using the CyanogenMod trees, use a command like this:
repo init -u git://github.com/CyanogenMod/android.git -b cm-13.0
Then to sync up:
repo sync
Please see the CyanogenMod Wiki for building instructions, by device.
For more information on this Github Organization and how it is structured, please read the wiki article
Buildbot
All supported devices are built nightly and periodically as changes are committed to ensure the source trees remain buildable.
You can view the current build statuses in the Jenkins tool.