Go to file
prescott66 ba2ec9ee19 android-vendor-cm: Renamed T-Mobile SK to Telekom SK in APNs list
Change-Id: I70823318ec3ee9d3e7db6c414f3e1ceb5d8ad9cc
2013-07-23 17:38:38 +00:00
bash_completion repo bash completion: _find_repo: improve check 2013-05-05 21:37:17 -07:00
config Rename Babel to VoicePlus 2013-07-21 09:34:19 -07:00
overlay Merge "Add Ukrainian dictionary." into cm-10.1 2013-04-13 02:14:06 -07:00
prebuilt/common android-vendor-cm: Renamed T-Mobile SK to Telekom SK in APNs list 2013-07-23 17:38:38 +00:00
.gitignore
CHANGELOG.mkdn
CONTRIBUTORS.mkdn update manta maintainers 2013-07-03 12:43:14 -07:00
get-prebuilts
LICENSE
README.mkdn
vendorsetup.sh tell curl to be quiet in vendorsetup.sh 2013-04-16 00:17:08 -05:00

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-10.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-10.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.