# Inconsistency in messages about --set-upstream from git pull and git branch

2 messages from 2012-12-01 to 2012-12-02. Participants: Dan Rosén, Carlos Martín Nieto.
Thread: https://gitlist.dev/t/32259

## Dan Rosén, 2012-12-01 15:36

Subject: Inconsistency in messages about --set-upstream from git pull and git branch
Message-ID: <CAN2DD_Hc4ZoQZefUirSZF=PZY5654yqrQfk5g1VzBLixEC=T-g@mail.gmail.com>
URL: https://gitlist.dev/e/CAN2DD_Hc4ZoQZefUirSZF%3DPZY5654yqrQfk5g1VzBLixEC%3DT-g%40mail.gmail.com

```
I added a new origin to a repository and did git pull and got this message:

 * [new branch]      master     -> origin/master
There is no tracking information for the current branch.
Please specify which branch you want to merge with.
See git-pull(1) for details

    git pull <remote> <branch>

If you wish to set tracking information for this branch you can do so with:

    git branch --set-upstream master origin/<branch>


I followed the instructions:
$ git branch --set-upstream master origin/master
The --set-upstream flag is deprecated and will be removed. Consider
using --track or --set-upstream-to
Branch master set up to track remote branch master from origin.

I was using git version 1.8.0 precompiled for Arch Linux.

I tried to find an issue tracker but perhaps it is appropriate to
report this inconsistency to this mailing list.

Best,
Dan

```

## Carlos Martín Nieto, 2012-12-02 01:29

Subject: Re: Inconsistency in messages about --set-upstream from git pull and git branch
Message-ID: <87y5hhjl6s.fsf@centaur.cmartin.tk>
URL: https://gitlist.dev/e/87y5hhjl6s.fsf%40centaur.cmartin.tk
In-Reply-To: <CAN2DD_Hc4ZoQZefUirSZF=PZY5654yqrQfk5g1VzBLixEC=T-g@mail.gmail.com>

```
Dan Rosén <danr@student.chalmers.se> writes:

>
>     git branch --set-upstream master origin/<branch>
>

This has been fixed already in 1.8.0.1

   cmn

```