Go to file
Ricardo Cerqueira a3d4971b2a CHANGELOG: Update maintainer list
Change-Id: Ied8f796a62a96b89b15a8204c3525575dfb00e65
2011-03-19 15:36:09 +00:00
overlay Merge "speedy: add device speedy to cyanogen vendor" into gingerbread 2011-03-19 11:29:54 +03:00
prebuilt
products Add ZERO product 2011-03-19 04:36:45 -04:00
tools
.gitignore
Android.mk
CHANGELOG
CHANGELOG.mkdn CHANGELOG: Update maintainer list 2011-03-19 15:36:09 +00:00
extract-gapps-files
extract-google-files
get-google-files Remove the obsolete gb-tegra GApps 2011-03-16 01:47:53 -05:00
get-rommanager
LICENSE
prelink-linux-arm-hero.map
prelink-linux-arm-msm722x.map
README.mkdn
vendorsetup.sh Add ZERO product 2011-03-19 04:36:45 -04: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