2015-12-15 17:32:54 +01:00
## Submitting Patches ##
2013-10-18 13:36:32 +02:00
------------------
2017-10-25 11:37:56 +02:00
Our project is open source, and patches are always welcome!
You can send patches by using:
2020-04-15 12:43:16 +02:00
2017-10-25 11:37:56 +02:00
Pull request, right here on git.
2013-10-18 13:36:32 +02:00
2017-10-25 11:37:56 +02:00
Contact @lj50036 on irc, Network: freenode, Channel: #twrp
2013-10-18 13:36:32 +02:00
2015-12-15 17:32:54 +01:00
## Maintaining Authorship ##
----------------------
2017-01-20 04:27:53 +01:00
Maintaining authorship is a very important aspect of working with Open Source code. If you wish to submit a patch/fix
2015-12-15 17:32:54 +01:00
from anywhere else (another ROM, project, etc.), it is imperative that you maintain the ownership of the person whose
2017-10-25 11:37:56 +02:00
work you are seeking to include. Doing so will ensure that credit is given where it is deserved, and the [principles of open source ](http://opensource.org/docs/osd )
2015-12-15 17:32:54 +01:00
are upheld. Your contribution to the project will still be recognized as you will forever be listed as the committer.
If you manually cherry pick a patch/fix then you will need to add the original author prior to pushing to our [gerrit ](https://gerrit.omnirom.org ).
This is a very easy task to perform, and is usually done after you commit a patch/fix locally. This is accomplished
after you type in `git commit -a` , type in the commit message and save. You would then do the following:
```bash
git commit --amend --author "Author < email @ address . com > "
```
2017-10-25 11:37:56 +02:00
So it should look like this once you get all of the author's information:
2015-12-15 17:32:54 +01:00
```bash
git commit --amend --author "Spencer McGillicuddy < spencer.the.bestest @ gmail . com > "
```
Alternatively, adding as part of the original `git commit` message is preferred and done like the following:
```bash
git commit --author="Author < email @ address . com > " -m "[commit message]"
```
This saves time, and when part of your normal routine, prevents the infamous "ermahgerd I forgot to add authorship -
let me fix it because I was found out!" message.
## Getting Started ##
2013-10-18 13:36:32 +02:00
---------------
2017-10-25 11:37:56 +02:00
To get started with OMNI sources to build TWRP, you'll need to get
2016-05-31 07:45:27 +02:00
familiar with [Git and Repo ](https://source.android.com/source/using-repo.html ).
2013-10-18 13:36:32 +02:00
2017-10-25 11:37:56 +02:00
To initialize your local repository using the OMNIROM trees to build TWRP, use a command like this:
2013-10-18 13:36:32 +02:00
2020-02-27 16:53:17 +01:00
repo init -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-10.0
2013-10-18 13:36:32 +02:00
2017-10-25 11:37:56 +02:00
To initialize a shallow clone, which will save even more space, use a command like this:
2013-10-18 13:36:32 +02:00
2020-02-27 16:53:17 +01:00
repo init --depth=1 -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-10.0
2013-10-18 13:36:32 +02:00
2017-10-25 11:37:56 +02:00
Then to sync up:
2020-04-15 12:43:16 +02:00
2017-10-25 11:37:56 +02:00
repo sync
2020-04-15 12:43:16 +02:00
2017-10-25 11:37:56 +02:00
Then to build for a device with recovery partition:
2020-04-15 12:43:16 +02:00
2017-10-25 11:37:56 +02:00
cd < source-dir > ; export ALLOW_MISSING_DEPENDENCIES=true; . build/envsetup.sh; lunch omni_< device > -eng; mka recoveryimage
2020-04-22 15:28:14 +02:00
2017-10-25 11:37:56 +02:00
Then to build for a device without recovery partition:
2020-04-22 15:28:14 +02:00
2017-10-25 11:37:56 +02:00
cd < source-dir > ; export ALLOW_MISSING_DEPENDENCIES=true; . build/envsetup.sh; lunch omni_< device > -eng; mka bootimage