git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
DRDan Rosén <danr@student.chalmers.se>
Date
Dec 1, 2012, 15:36 UTC
Message-ID
<CAN2DD_Hc4ZoQZefUirSZF=PZY5654yqrQfk5g1VzBLixEC=T-g@mail.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

Next: Carlos Martín Nieto
Message 1 of 2 in “Inconsistency in messages about --set-upstream from git pull and git branch”
  1. Dan RosénDec 1, 2012
  2. Carlos Martín NietoDec 2, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.