Go to file
Simon Josefsson 1ad1f1a341 Work around that 'make-key' has rc 1 on success.
The 'make_key' script returns rc 1 on both failure and success, so work
around by ignoring exit code from that script.
2017-03-04 10:26:45 +01:00
ambientsdk increment ambientsdk version 2016-09-13 14:41:43 -07:00
bash_completion Add a bash completion "--force-sync" for repo sync 2015-07-30 15:13:11 +08:00
build Merge remote-tracking branch 'lineageos/cm-13.0' into replicant-6.0 2017-02-12 19:41:06 +01:00
charger charger: Use the same metrics as recovery to pick a density 2016-10-13 13:30:36 +01:00
cmsdk update cmsdk api files to latest version 2016-12-13 02:11:57 +01:00
config Merge remote-tracking branch 'lineageos/cm-13.0' into replicant-6.0 2017-02-12 19:41:06 +01:00
gello http_prebuilt: Implement archive of artifacts 2017-01-08 15:58:48 +00:00
overlay Merge remote-tracking branch 'lineageos/cm-13.0' into replicant-6.0 2017-02-12 19:41:06 +01:00
prebuilt Merge remote-tracking branch 'lineageos/cm-13.0' into replicant-6.0 2017-02-12 19:41:06 +01:00
sepolicy Merge branch 'cm-13.0' of https://github.com/CyanogenMod/android_vendor_cm into replicant-6.0 2016-12-12 13:09:51 +01:00
.gitignore Merge remote-tracking branch 'lineageos/cm-13.0' into replicant-6.0 2017-02-12 19:41:06 +01:00
build-toolchain build-toolchain: more common path for gold ld 2017-02-18 16:28:59 +01:00
CHANGELOG.mkdn Merge remote-tracking branch 'lineageos/cm-13.0' into replicant-6.0 2017-02-12 19:41:06 +01:00
CONTRIBUTORS.mkdn Merge remote-tracking branch 'lineageos/cm-13.0' into replicant-6.0 2017-02-12 19:41:06 +01:00
get-prebuilts Merge remote-tracking branch 'github/cm-13.0' into replicant-6.0 2015-12-17 18:24:03 +01:00
LICENSE cm: Rebrand to LineageOS 2016-12-29 12:39:54 +08:00
README.mkdn Merge remote-tracking branch 'lineageos/cm-13.0' into replicant-6.0 2017-02-12 19:41:06 +01:00
sign-build Work around that 'make-key' has rc 1 on success. 2017-03-04 10:26:45 +01:00
targets add i9305 to targets 2017-01-27 21:39:56 +01:00
vendorsetup.sh vendorsetup: match lineage naming for build roster 2017-01-14 15:09:05 -08:00

Replicant

About

Replicant is a fully free Android distribution running on several devices, a free software mobile operating system putting the emphasis on freedom and privacy/security.

More information about Replicant is available at: http://www.replicant.us/about.php

Website: http://www.replicant.us/ Blog: http://blog.replicant.us/ Wiki/tracker/forums: http://redmine.replicant.us/

Copying

Replicant is made of free software, owned by various copyright holders and released under various free software licenses. Please refer to the source code of each component for specific details.

LineageOS

Submitting Patches

Patches are always welcome! Please submit your patches via LineageOS 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 LineageOS Code Review

Getting Started

To get started with Android/LineageOS, you'll need to get familiar with Repo and Version Control with Git.

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

repo init -u git://github.com/LineageOS/android.git -b cm-13.0

Then to sync up:

repo sync

Please see the LineageOS 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.