All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miles Bader <miles@gnu.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Martin Fick" <mfick@codeaurora.org>,
	"SZEDER Gábor" <szeder@ira.uka.de>,
	"Daly Gutierrez" <daly.gutierrez@gmail.com>,
	git@vger.kernel.org
Subject: Re: Recovering Committed Changes in a Detached Head?
Date: Mon, 10 Oct 2011 10:26:06 +0900	[thread overview]
Message-ID: <87sjn1fxht.fsf@catnip.gol.com> (raw)
In-Reply-To: <7vfwj1px6h.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Sun, 09 Oct 2011 16:22:46 -0700")

Junio C Hamano <gitster@pobox.com> writes:
>> First, maybe git could create refs for these automatically, perhaps
>> with a name like orphans/1?  Maybe these refs would only be visible
>> via git branch --orphans.
>
> Instead of spelling them orphans/$n, you already have @{$n}.

Hmm, shouldn't that be "HEAD@{$n}" (as the reflog output suggests)?

[Well, I dunno, I'm generally kind of confused by the @{...} notation,
but I just tried it out, and just @{$n} seems to refer to the current
branch, which presumably won't include the orphaned bit once one it's
been orphaned...]

Thanks,

-Miles

-- 
`The suburb is an obsolete and contradictory form of human settlement'

      reply	other threads:[~2011-10-10  1:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-08 20:58 Recovering Committed Changes in a Detached Head? Daly Gutierrez
2011-10-08 21:37 ` SZEDER Gábor
2011-10-08 22:00   ` Martin Fick
2011-10-09  3:32     ` Joel C. Salomon
2011-10-09  5:39       ` Martin Fick
2011-10-09  5:52     ` Nguyen Thai Ngoc Duy
2011-10-09  7:46       ` Ronan Keryell
2011-10-09  8:12     ` Matthieu Moy
2011-10-09 23:22     ` Junio C Hamano
2011-10-10  1:26       ` Miles Bader [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=87sjn1fxht.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --cc=daly.gutierrez@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mfick@codeaurora.org \
    --cc=szeder@ira.uka.de \
    /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.