git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergio Callegari <scallegari@arces.unibo.it>
To: git@vger.kernel.org
Subject: fsck missing dangling commits that are candidate heads?
Date: Tue, 3 Apr 2007 19:41:26 +0000 (UTC)	[thread overview]
Message-ID: <loom.20070403T213135-68@post.gmane.org> (raw)

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? 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.

And finally...

Also git gc --prune seems to miss the commit... so when we gc useless objects
appear to be kept around.

Is this correct?

Thanks,

Sergio

             reply	other threads:[~2007-04-03 19:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-03 19:41 Sergio Callegari [this message]
2007-04-03 19:47 ` fsck missing dangling commits that are candidate heads? 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

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=loom.20070403T213135-68@post.gmane.org \
    --to=scallegari@arces.unibo.it \
    --cc=git@vger.kernel.org \
    /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).