From: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
To: Heiko Voigt <hvoigt@hvoigt.net>
Cc: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>,
git@vger.kernel.org
Subject: Re: [1.8.0] git checkout refs/heads/foo checks out branch foo
Date: Mon, 7 Feb 2011 19:22:21 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.1.10.1102071918430.3788@debian> (raw)
In-Reply-To: <20110207211127.GG63976@book.hvoigt.net>
On Mon, 7 Feb 2011, Heiko Voigt wrote:
> Hallo Martin,
>
> On Mon, Feb 07, 2011 at 06:01:51AM -0500, Martin von Zweigbergk wrote:
> > Proposal:
> >
> > 'git checkout refs/heads/foo' (or 'git checkout heads/foo' for that
> > matter) does not check out the branch, but instead detaches HEAD at
> > foo. This is quite counter-intuitive (at least to me) and the same
> > functionality can be achieved by using e.g. foo~0. Change the behavior
> > so that the branch is actually checked out. This also applies to
> > e.g. 'git rebase master refs/heads/topic', which currently rebases a
> > detached HEAD. There are probably other examples as well that I'm not
> > aware of.
>
> Just to clarify: You are not proposing that 'git checkout origin/master'
> would also not checkout to a detached head, right? Because that is a
> feature I am using frequently to test branches that have been pushed by
> another developer to a remote server. If that would create a new local
> branch that would be confusing.
Nope, I'm not proposing that. I wouldn't want that either.
/Martin
prev parent reply other threads:[~2011-02-08 0:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 11:01 [1.8.0] git checkout refs/heads/foo checks out branch foo Martin von Zweigbergk
2011-02-07 20:53 ` Junio C Hamano
2011-02-07 20:59 ` Jeff King
2011-02-07 21:36 ` Sverre Rabbelier
2011-02-07 22:00 ` Jonathan Nieder
2011-02-07 23:37 ` Junio C Hamano
2011-02-07 23:45 ` Jeff King
2011-02-08 0:01 ` Jonathan Nieder
2011-02-08 0:28 ` Jeff King
2011-02-08 0:31 ` Martin von Zweigbergk
2011-02-08 0:52 ` [PATCH/WIP] checkout: introduce --detach synonym for "git checkout foo^{commit}" Jonathan Nieder
2011-02-08 0:55 ` Jonathan Nieder
2011-02-08 10:26 ` [PATCH v2 0/3] " Jonathan Nieder
2011-02-08 10:29 ` [PATCH 1/3] checkout: split off a function to peel away branchname arg Jonathan Nieder
2011-02-08 10:32 ` [PATCH 2/3] checkout: introduce --detach synonym for "git checkout foo^{commit}" Jonathan Nieder
2011-02-08 10:34 ` [PATCH 3/3] checkout: rearrange update_refs_for_switch for clarity Jonathan Nieder
2011-02-07 21:11 ` [1.8.0] git checkout refs/heads/foo checks out branch foo Heiko Voigt
2011-02-08 0:22 ` Martin von Zweigbergk [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=alpine.DEB.1.10.1102071918430.3788@debian \
--to=martin.von.zweigbergk@gmail.com \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.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 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.