Go to file
Adnan Begovic 4534c7ae3b vendor/cm: Expose internal revision for platform.
TICKET: CYNGNOS-724
Change-Id: I9d93ca77fd888046cb4733a73ace2ee337c46300
2015-08-11 16:00:48 -07:00
bash_completion
build vendor/cm: Always use gpg sign-and-deploy for deployments. 2015-08-07 13:28:56 -07:00
config vendor/cm: Expose internal revision for platform. 2015-08-11 16:00:48 -07:00
overlay cmsdk: Dual SIM support on CM SDK 2015-08-07 01:32:30 +01:00
prebuilt/common Add new Tuenti MNC SPN override name 2015-08-11 13:45:14 -07:00
sepolicy cmsdk: Dual SIM support on CM SDK 2015-08-07 01:32:30 +01:00
.gitignore
CHANGELOG.mkdn
CONTRIBUTORS.mkdn
LICENSE
README.mkdn
vendorsetup.sh

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-12.1 .
(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-12.1

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.