git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: fsck missing dangling commits that are candidate heads?

From
SCSergio Callegari <scallegari@arces.unibo.it>
Date
Apr 3, 2007, 19:56 UTC
Message-ID
<loom.20070403T215123-220@post.gmane.org>
In-Reply-To
<20070403194750.GG27706@spearce.org>
Shawn O. Pearce <spearce <at> spearce.org> writes:
Show 10 quoted lines
>
> Right.  This is the reflog in action.  Your current branch has two
> reflogs, .git/logs/HEAD and .git/logs/refs/heads/$foo, where $foo
> is your current branch name.  Both of these logs mention the commit
> you are looking for, so they aren't considered dangling garbage,
> nor are they pruneable.
> 
> Use `git log -g` or `git log -g $foo` to look at the reflog for
> HEAD and $foo to locate the commit in question.
>

Many thanks! I was quite sure I was missing something... At least I am in good company since the fsck man page does not mention the logs :-)

Then... is there any shorthand for finding candidate branch-heads (i.e. for having something like fsck without looking at the logs) ?

Previous: Shawn O. PearceNext: Sergio Callegari
Message 3 of 7 in “fsck missing dangling commits that are candidate heads?”
  1. Sergio CallegariApr 3, 2007
  2. Shawn O. PearceApr 3, 2007
  3. Sergio CallegariApr 3, 2007
  4. Sergio CallegariApr 4, 2007
  5. Shawn O. PearceApr 4, 2007
  6. Sergio CallegariApr 4, 2007
  7. Nicolas PitreApr 3, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.