All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raimund Bauer <ray007@gmx.net>
To: git@vger.kernel.org
Subject: 2 things about branches
Date: Mon, 19 Feb 2007 19:13:59 +0100	[thread overview]
Message-ID: <1171908840.10817.21.camel@localhost> (raw)

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

             reply	other threads:[~2007-02-19 18:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-19 18:13 Raimund Bauer [this message]
2007-02-19 18:37 ` 2 things about branches J. Bruce Fields

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1171908840.10817.21.camel@localhost \
    --to=ray007@gmx.net \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.