Workstart-gerrit Submission Considerations

Source: Internet
Author: User

About the process of bug storage?
--first try to ensure that their own changes to the basic source code is the latest, this time you can check the source update status, git log, and then git pull a bit, and then git St. Check the local library changes
-After you have ensured the status of the latest, this time can modify the source code
--After the completion of the modification, the source code compilation, push to the phone, view the results of the changes, this time to try to test the results in a variety of circumstances, to ensure the robustness of the program after modification
--this time do the following
git Add. (Commit changes to cache)
Git commit (commit changes to local git library)
Git show HEAD (view change status)
Repo upload. (update local status to Server library)
git br-av (View branch and latest status)
--Login to your Gerrit interface
--click on the May (login password is 125116!! SSDD)
--View your own changes (focus on whether your code has been modified correctly, and whether the branch is correct)
--Copy the URL and change the description, in the UI group inside, the enactment person review, oneself put review state +1

Problems encountered
--The first time repo upload, always failed, prompted that their mailbox is not correct
Workaround: The original configuration Gerrit error, change the following

git config--global--list (view your registration information)
git config--global user.email "[Email protected]"
-This is not the point, the key is that the commit already exists in the local git library, all need to resume the commit
git reset HEAD (this is to revert to the previous version, this is deleted as if the cache area content)
git reset--hard HEAD (this restores the cache with the local working directory tree)
When we want to recover, we have to go back to the front of our own node as if we could.

Workstart-gerrit Submission Considerations

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.