Just, FYI, "git checkout master" automatically does the tracking of a
remote branch with the same name by convention. This is due to the
"branch.autosetupmerge" configuration switch being on by default.
On Wednesday, June 27, 2012 2:16:15 PM UTC+2, mike wrote:
> I managed to do the following:
> git checkout master
> Branch master set up to track remote branch master from origin.
> Switched to a new branch 'master'
> Then I merged release-2.2.16 to this branch. When done I pushed it.
> I checked and remote master now contains my changes.
> Thanks for all help!
> On Wednesday, June 27, 2012 1:41:41 PM UTC+2, Thomas Ferris Nicolaisen
>> On Wednesday, June 27, 2012 12:38:07 PM UTC+2, mike wrote:
>>> You've just checked out a commit as your HEAD that is the head of the
>>>> origin/master branch. But you need to checkout a new branch master
>>>> that will be a copy (local fork) of the origin/master or more probably
>>>> you need to checkout your existing master and merge origin/master into
>>> How can I do that? Which command? Or do I do it from Eclipse? ( Attach
>>> picture from Eclipse).
>> Can you try checking out "origin/master" as a local tracking branch
>> On the command line you can do it like this:
>> git checkout -t origin/master
>> In Eclipse, maybe you can right-click the origin/master branch under
>> "Remote tracking" folder, and do something like "track locally". Not sure
>> as I haven't got Eclipse running here.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To view this discussion on the web visit
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at