Re: fsck missing dangling commits that are candidate heads?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Shawn O. Pearce <spearce <at> spearce.org> writes:

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



-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]