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

2 things about branches

From
RBRaimund Bauer <ray007@gmx.net>
Date
Feb 19, 2007, 18:13 UTC
Message-ID
<1171908840.10817.21.camel@localhost>

I think it's a good idea to not list remote branches in 'git branch' output per default, but imho we should make an exception for the branch the user is currently on. Currently when I do 'git checkout origin/next' the checkout works fine and I get the warning about the remote branch, but an informational query 'git branch' right after that says

* (no branch)
  master

'git branch -r' also doesn't mark me as being on origin/next. Maybe we could query the remote-branches for a matching ref this case?

And another wish about branches: After a fresh clone of git, my .git/config contains a section

[branch "master"]
        remote = origin
        merge = refs/heads/master

so it's easy to keep the branch updated by just saying 'git pull' when on branch master.

Doing 'git checkout -b next origin/next' gives me my own next-branch, but short of editing .git/config there seems to be no way to get a similar section [branch "next"] ... so I can follow next as easy as master. I'm not sure if there exists a sane default we could use automatically, but maybe a switch to git-checkout to write a config entry would be possible?

Thanks for listening to my rambling
-- 
best regards

  Ray
Next: J. Bruce Fields
Message 1 of 2 in “2 things about branches”
  1. Raimund BauerFeb 19, 2007
  2. J. Bruce FieldsFeb 19, 2007

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.