From: "Joel C. Salomon" <joelcsalomon@gmail.com>
To: git@vger.kernel.org
Cc: mfick@codeaurora.org, szeder@ira.uka.de, daly.gutierrez@gmail.com
Subject: Re: Recovering Committed Changes in a Detached Head?
Date: Sat, 08 Oct 2011 23:32:00 -0400 [thread overview]
Message-ID: <4E9115B0.3030701@gmail.com> (raw)
In-Reply-To: <ab706826-75df-4410-941e-6b40ec92713c@email.android.com>
On 10/08/2011 06:00 PM, Martin Fick wrote:
>> git reflog to the rescue.
<snip>
>> There you see the first line of the commit message from your "lost"
>> commit, and you can do
>>
>> git checkout -b lost_detached_head 92aa5381
>>
>> and you get a branch pointing to that commit you made while on
>> detached head, and you can work with it as usual.
>
> While rflog is cool, I can't help but think that git could be even more helpful for these scenarios.
>
> 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.
Creating these "orphan" refs would require the equivalent of (part of)
git-fsck; I can't imagine that could be imposed without significant
overhead on too many operations. I think you'd be better off wrapping
git-fsck in a script that can create these branches.
--Joel
next prev parent reply other threads:[~2011-10-09 3:32 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 [this message]
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
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=4E9115B0.3030701@gmail.com \
--to=joelcsalomon@gmail.com \
--cc=daly.gutierrez@gmail.com \
--cc=git@vger.kernel.org \
--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.