gyliu513

Git global setup

git config --global user.name "Guangya Liu"
git config --global user.email "gyliu@apache.com"

git config --global user.name "Guangya Liu"
git config --global user.email "gyliu513@gmail.com"

git config user.name "Guangya Liu"
git config user.email "gyliu513@gmail.com"

gyliu513

505  git remote -v
  506  git fetch upsteram
  507  git fetch upstream
  508  git branch
  509  git merge upstream/master
  510  git branch
  511  git branch -r
  512  git checkout k8s_25349
  513  git rebase master
  514  ls

gyliu513

In Getting Started with Homebrew, I talked about what the Homebrew package management system is, why you’d want to use it, and how to install it and access its basic functionality.

This post expands upon those basic ideas by talking about how to keep your Homebrew up to date — and so ensure it’s doing its job optimally.

Tip #1: Update Your Homebrew
You want to always ensure that you’re running the newest version of Homebrew and that it has the newest list of formulae available from the main repository. This is done with the “brew update” command:


$ brew update
Already up-to-date.

gyliu513

git config --global http.proxy http://9.21.54.14:3128
git config --global https.proxy https://9.21.54.14:3128
git config --global --unset http.proxy
git config --global --unset https.proxy
npm config delete proxy

gyliu513

Add dependency

When you want to start new work that is based on the commit under the review, you can add the commit as a dependency.
#fetch change under review and check out branch based on that change.
git review -d $PARENT_CHANGE_NUMBER
git checkout -b $DEV_TOPIC_BRANCH
# Edit files, add files to git
git commit 
git review
NOTE: git review rebases the existing change (the dependency) and the new commit if there is a conflict against the branch they are being proposed to. Typically this is desired behavior as merging cannot happen until these conflicts are resolved. If you don't want to deal with new patchsets in the existing change immediately you can pass the -R option to git review in the last step above to prevent rebasing. This requires future rebasing to resolve conflicts.