From: Nicolas Pitre <nico@cam.org>
To: Sergio Callegari <scallegari@arces.unibo.it>
Cc: git@vger.kernel.org
Subject: Re: fsck missing dangling commits that are candidate heads?
Date: Tue, 03 Apr 2007 15:53:14 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0704031551090.28181@xanadu.home> (raw)
In-Reply-To: <loom.20070403T213135-68@post.gmane.org>
On Tue, 3 Apr 2007, Sergio Callegari wrote:
> Hi,
>
> on git 1.5.0.6, I have done the following:
>
> work work
>
> git commit -a
>
> git reset HEAD^ (assume a mistake)
>
> git fsck
>
> the last fsck shows nothing...
> Is this correct?
Yes.
> Shouldn't the latest commit (the one made unreachable by the
> reset) be reported as dangling and as a candidate branch head?
>
> Also git lost-found misses the commit...
> But it is there... I can find it manually in the object database and tag it.
It is not lost. Try git log -g and you'll probably find it there... at
least until the reflog entry corresponding to it gets expired.
Nicolas
prev parent reply other threads:[~2007-04-03 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 19:41 fsck missing dangling commits that are candidate heads? Sergio Callegari
2007-04-03 19:47 ` Shawn O. Pearce
2007-04-03 19:56 ` Sergio Callegari
2007-04-04 13:32 ` Sergio Callegari
2007-04-04 14:46 ` Shawn O. Pearce
2007-04-04 20:08 ` Sergio Callegari
2007-04-03 19:53 ` Nicolas Pitre [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.LFD.0.98.0704031551090.28181@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=scallegari@arces.unibo.it \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).