All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Hudec <bulb@ucw.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [BUG?] Detaching head at checked out point does not work.
Date: Sat, 12 May 2007 22:18:15 +0200	[thread overview]
Message-ID: <20070512201815.GC8983@efreet.light.src> (raw)
In-Reply-To: <7vd515ygw5.fsf@assigned-by-dhcp.cox.net>

[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]

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>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2007-05-12 20:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-12 17:21 [BUG?] Detaching head at checked out point does not work Jan Hudec
2007-05-12 18:26 ` Junio C Hamano
2007-05-12 19:18   ` Jan Hudec
2007-05-12 19:35     ` Junio C Hamano
2007-05-12 20:18       ` Jan Hudec [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=20070512201815.GC8983@efreet.light.src \
    --to=bulb@ucw.cz \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.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.