Go to file
Steve Kondik 48f8df8ddb extract-utils: Add pinning support
* In many cases, we would like to keep certain files which do not
   exactly match what might be extracted from a factory ROM. This
   becomes extremely annoying over time to manually reconstruct,
   and it's easy to miss these special cases when updating to a
   new vendor release. It's also useful to flag additions which
   aren't found in the upstream release at all.
 * To solve this, we can now "pin" files to a specific sha1 hash.
   Simply append the sha1sum of the file to the appropriate line
   in your bloblist, prepended by a | delimiter.
 * This works by backing up the current files first, running the
   extraction, then checking if any pinned files need to be
   restored.
 * Also add an exit trap to clean up all of our tempfiles

Change-Id: I2010b5175b5701e19a3efb112e8907062ca37d66
2016-08-14 14:10:53 -07:00
ambientsdk Update ambientsdk version 1.5.11 2016-05-24 15:33:46 -07:00
bash_completion Add a bash completion "--force-sync" for repo sync 2015-07-30 15:13:11 +08:00
build extract-utils: Add pinning support 2016-08-14 14:10:53 -07:00
config config: Add WeatherManagerService to PRODUCT_PACKAGES 2016-08-13 01:34:17 -07:00
gello Gello artifact: v29 2016-07-29 13:02:12 -07:00
overlay cm: overlay: enable otg notification 2016-07-05 10:46:26 -07:00
prebuilt/common Tele2 (LT) APN updates 2016-08-03 03:43:05 -07:00
sepolicy sepolicy: Move new QCOM-specific policy to the right place 2016-08-09 00:07:19 -07:00
.gitignore gitignore 2010-06-27 20:11:11 -07:00
CHANGELOG.mkdn Updated CHANGELOG and (c) date 2015-11-10 17:28:12 +01:00
CONTRIBUTORS.mkdn contributors: update Galaxy Nexus maintainers 2016-08-10 09:06:13 -07:00
LICENSE Updated CHANGELOG and (c) date 2015-11-10 17:28:12 +01:00
README.mkdn Updates for cm-13.0 2015-10-07 21:15:52 +03:00
vendorsetup.sh Updates for cm-13.0 2015-10-07 21:15:52 +03:00

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.