threads / bug / 8116
Subject: [BUG?] Detaching head at checked out point does not work.
Hello,
I can correctly detach head by saying:
git checkout master^0
(or git checkout master^{} or git checkout refs/heads/master), but NONE of these work, if I currently have master checked out. Shouldn't it detach anyway?
Regards,
Jan
-- Jan 'Bulb' Hudec <bulb@ucw.cz>
Junio C HamanoRe: [BUG?] Detaching head at checked out point does not work.
Jan Hudec <bulb@ucw.cz> writes:
> Hello,
>
> I can correctly detach head by saying:
>
> git checkout master^0
>
> (or git checkout master^{} or git checkout refs/heads/master), but NONE of
> these work, if I currently have master checked out. Shouldn't it detach
> anyway?Yes, and it does as far as I know.
Do you have 3e0318a3?
commit 3e0318a3613ae8e89dcb1fc39d909145e64287b9 Author: Junio C Hamano <junkio@cox.net> Date: Thu Mar 29 01:02:50 2007 -0700
checkout: allow detaching to HEAD even when switching to the tip of a branch
You cannot currently checkout the tip of an existing branch
without moving to the branch.
This allows you to detach your HEAD and place it at such a
commit, with:
$ git checkout master^0
Signed-off-by: Junio C Hamano <junkio@cox.net>Re: [BUG?] Detaching head at checked out point does not work.
On Sat, May 12, 2007 at 11:26:53 -0700, Junio C Hamano wrote:
> Jan Hudec <bulb@ucw.cz> writes:
>
> > Hello,
> >
> > I can correctly detach head by saying:
> >
> > git checkout master^0
> >
> > (or git checkout master^{} or git checkout refs/heads/master), but NONE of
> > these work, if I currently have master checked out. Shouldn't it detach
> > anyway?
>
> Yes, and it does as far as I know.
>
> Do you have 3e0318a3?It does not seem to be in 1.5.1.4, so no, I don't.
I apologise for not looking whether head has a fix.
-- Jan 'Bulb' Hudec <bulb@ucw.cz>
Junio C HamanoRe: [BUG?] Detaching head at checked out point does not work.
Jan Hudec <bulb@ucw.cz> writes:
> On Sat, May 12, 2007 at 11:26:53 -0700, Junio C Hamano wrote:
>> Jan Hudec <bulb@ucw.cz> writes:
>>
>> > I can correctly detach head by saying:
>> >
>> > git checkout master^0
>> >
>> > (or git checkout master^{} or git checkout refs/heads/master), but NONE of
>> > these work, if I currently have master checked out. Shouldn't it detach
>> > anyway?
>>
>> Yes, and it does as far as I know.
>>
>> Do you have 3e0318a3?
>
> It does not seem to be in 1.5.1.4, so no, I don't.As that commit is directly on top of v1.5.1, I think it may not hurt to cherry-pick that single commit to 'maint' for 1.5.1.5, although some may argue that it is not strictly a bugfix but a new feature.
Re: [BUG?] Detaching head at checked out point does not work.
On Sat, May 12, 2007 at 12:35:22 -0700, Junio C Hamano wrote:
> Jan Hudec <bulb@ucw.cz> writes:
>
> > On Sat, May 12, 2007 at 11:26:53 -0700, Junio C Hamano wrote:
> >> Jan Hudec <bulb@ucw.cz> writes:
> >>
> >> > I can correctly detach head by saying:
> >> >
> >> > git checkout master^0
> >> >
> >> > (or git checkout master^{} or git checkout refs/heads/master), but NONE of
> >> > these work, if I currently have master checked out. Shouldn't it detach
> >> > anyway?
> >>
> >> Yes, and it does as far as I know.
> >>
> >> Do you have 3e0318a3?
> >
> > It does not seem to be in 1.5.1.4, so no, I don't.
>
> As that commit is directly on top of v1.5.1, I think it may not
> hurt to cherry-pick that single commit to 'maint' for 1.5.1.5,
> although some may argue that it is not strictly a bugfix but a
> new feature.I would not call it a new feature, since it worked if I had something else than master checked out. It is not a regression though and given that 1.5.2 is getting closer I'm not sure it's worth bothering.
-- Jan 'Bulb' Hudec <bulb@ucw.cz>