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

Re: Tracking remote branches

From
NSNicolas Sebrecht <nicolas.s.dev@gmx.fr>
Date
Sep 14, 2009, 05:01 UTC
Message-ID
<20090914050145.GA12985@vidovic>
In-Reply-To
<a4c8a6d00909131737v35d7c63dsea669f47456f5acb@mail.gmail.com>
The 13/09/09, Thiago Farina wrote:
> Hi,
> 
> I know that I could do simply, instead of above:
> $ git checkout --track -b maint origin/maint

Or $ git checkout -t origin/maint

Show 12 quoted lines
> OK, now I switched to maint branch. And then I did:
> $ git status
> 
> # On branch maint
> # Changes to be committed
> #    (use "git reset HEAD <file>..." to unstage)
> #
> #          new file:    git-remote-curl
> #          new file:    git-replace
> #
> 
> What happened here? What I have to do now?

You've probably added these files to the index, mistakenly. If you don't have uncommited changes, try :

  git checkout -f master
  git branch -D maint
  git checkout -t origin/maint
  git status
The files should now be shown as "Untracked files".
-- 
Nicolas Sebrecht
Previous: Thiago FarinaNext: Thiago Farina
Message 2 of 4 in “Tracking remote branches”
  1. Thiago FarinaSep 14, 2009
  2. Nicolas SebrechtSep 14, 2009
  3. Thiago FarinaSep 14, 2009
  4. Heiko VoigtSep 14, 2009

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.