Maybe you will find some android native problems when you are developing android, then you can submit an issue to the google issue website. Of course, when submitting, it is best to first search whether there is a relevant CR submitted on the google issue After that, you can refer to the analysis of the coders who encountered this problem. You can also discuss with everyone if you apply for a gmail account, then if you want to submit your modifications to the problem to the android repository What should I do? That's what this article is about: how to submit your changes to Android gerrit.
First, let's get to know the two official websites:
1.android issue list
url： http://code.google.com/p/android/issues/list
This website will have all the issues currently submitted to android, here you can submit issues, manage your issues, or search for existing issues
2.android gerrit
url：https://android-review.googlesource.com
There will be all submissions on the android release on this website, you can view all submissions, manage your own submissions, and add android & google people
Review your commits.
After understanding the above two official websites, we will prepare to submit the code. The premise is that the code you need to submit is ready. I mainly describe the process based on my experience of submitting the code for the first time. If you want to want
To see the official detailed instructions, you can see the description of the Submitting Patches page of the android official website.
Based on the local (ubuntu) android source code drop students, submit the code to the android warehouse steps
1. Modify your code and verify OK
2. Configure android gerrit
1) Login to https://android-review.googlesource.com with gmail
2) Click on the username in the upper right corner to enter settings ---> Agreements ---> New Contributor Agreement and go all the way to various agreements (if you can't find any agreement, visit: https://cla.developers.google .com/clas and create one.)
3) Go to establish a password and follow the instructions to execute it in the local shell and it will be ok
3.cd Modify the .git directory of the repository where the code is located
vi config
Add the remote information of aosp as follows, taking 5.0 frameworks/webview as an example
[remote "aosp"]
url = https://android.googlesource.com/platform/frameworks/webview
review = https://android-review.googlesource.com
projectname = platform/frameworks/webview
fetch = +refs/heads/*:refs/remotes/aosp/*
4.1) git fetch aosp # fetch aosp remote repository
2) git branch -r |grep aosp
After the fetch is completed, you can see the following aosp-related branches through the above command
aosp/chromium-dev
aosp/idea133
aosp/idea133-weekly-release
aosp/jb-mr2-dev
aosp/master
aosp/tools_r22.2
3) git checkout -b aosp_master aosp/master #Create a local aosp_master branch
4) git config user.name "XXX" #Configure the submitted username and email address, the name and email here need to be
It is consistent with the profile under user settings on android-review.googlesource.com.
git config user.email [email protected]
5) git add, git commit These commands are almost not mentioned every day, pay attention to git log to see the submitted message must be
User information (name&email) on android gerrit, otherwise the submission will fail, and the error message is similar to the following:
remote: ERROR: In commit 2a34a535511c4e4b6f6baf91b6eedca2fcb37a1a
remote: ERROR: committer email address [email protected]
remote: ERROR: does not match your user account.
remote: ERROR:
remote: ERROR: The following addresses are currently registered:
remote: ERROR: [email protected]
6) repo upload . --br aosp_master # Submit to android gerrit, yes all the way
7) Find the module owner name in the module you modified, add them on gerrit to review your code
Dangdang.... Go to android-review.googlesource.com to check that your submission has gone up~~
Reprinted from: https://blog.csdn.net/annaload/article/details/42524289
Thank you