Go to file
2012-02-18 23:55:31 +03:00
config Add CM_SNAPSHOT ro.cm.version label option for SNAPSHOT builds. 2012-02-18 14:34:37 -05:00
overlay Add Greek dictionary 2012-01-21 16:26:40 +02:00
prebuilt/common backuptool: Deal with multiple files with the same name 2012-02-18 12:28:37 -08:00
tools Fix squisher for cm.version 2011-12-29 22:57:04 -05:00
.gitignore
CHANGELOG.mkdn Changelog: Saga contributor update. 2012-01-08 20:05:34 +00:00
get-prebuilts Allow get-prebuilts to work from any CWD 2012-01-02 18:58:50 -07:00
LICENSE Add LICENSE file 2011-01-30 21:10:08 -05:00
README.mkdn cm: Update README 2011-01-16 03:57:45 -06:00
vendorsetup.sh add epicmtd to lunch combo 2012-01-31 16:56:51 -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 gingerbread .
(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 Git and Repo.

To initialize your local repository using the CyanogenMod trees, use a command like this:

repo init -u git://github.com/CyanogenMod/android.git -b gingerbread

Then to sync up:

repo sync

Please see the CyanogenMod Wiki for building instructions.

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 at buildbot.teamdouche.net