From: "J. Bruce Fields" <bfields@fieldses.org>
To: Raimund Bauer <ray007@gmx.net>
Cc: git@vger.kernel.org
Subject: Re: 2 things about branches
Date: Mon, 19 Feb 2007 13:37:03 -0500 [thread overview]
Message-ID: <20070219183703.GB29930@fieldses.org> (raw)
In-Reply-To: <1171908840.10817.21.camel@localhost>
On Mon, Feb 19, 2007 at 07:13:59PM +0100, Raimund Bauer wrote:
> 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.
That's because you're not really "on" origin/next. Your currently
checked-out state happens to be the same as the state that origin/next
points at, but that's not quite the same thing. The main difference
being that if you commit something, origin/next won't be moved forward
to point at the new commit.
> Maybe we could query the remote-branches for a matching ref this case?
If that's what you want you could use e.g.
git describe --all
--b.
prev parent reply other threads:[~2007-02-19 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 18:13 2 things about branches Raimund Bauer
2007-02-19 18:37 ` J. Bruce Fields [this message]
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=20070219183703.GB29930@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=ray007@gmx.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox