Re: Issue 2100: Explanation of branches for CG (issue 5539062)

[dak]

On 2012/01/17 21:31:01, janek wrote:

http://codereview.appspot.com/5539062/diff/3004/Documentation/contributor/source-code.itexi
> File Documentation/contributor/source-code.itexi (right):


http://codereview.appspot.com/5539062/diff/3004/Documentation/contributor/source-code.itexi#newcode297
> Documentation/contributor/source-code.itexi:297: git branch dev/cg
> There is one possible downside of tracking master explicitly (if i
understand
> correctly how this works): if someone makes a mistake and calls 'git
push' while
> being on local branch which tracks master, this would result in
commits pushed
> to master.

Not quite.  "git push" pushes all tracking branches with a name that is
the same in the local repository as well as in the remote repository.

So if you have a local branch "master" tracking origin/master, this will
get pushed upstream when saying "git push" even if the currently
checked-out branch is a different one.

I only push with explicit branch specifications for that reason.  Got
bitten more than once.

http://codereview.appspot.com/5539062/