Duy Nguyen <pclo...@gmail.com> writes: > On Mon, Aug 12, 2013 at 3:37 PM, David Jeske <dav...@gmail.com> wrote: >> Is there currently any way to say "hey, git, show me what commits are >> dangling that might be lost in the reflog?" > > How do you define dangling commits? When you do "git commit --amend", > the current commit will become dangling (in the sense that it's not > referred by any ref, but the commit exists) and those are just noise > in my opinion.
"fsck lost-and-found" would be one way. It would be nice if we had something like (note: the following will _NOT_ work) git log -g HEAD --not --branches to say "walk the reflog of HEAD, but exclude anything that can be reached from the tips of branches". -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html