Re: ephemeral-branches instead of detached-head?
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 13, 2013, 16:49 UTC
- Message-ID
- <7vk3jpy1qt.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <CACsJy8Dke6Pezqsdcjzejc_cWCgOGTGs8LifjM2h2TQJy7N4HA@mail.gmail.com>
Duy Nguyen <pclouds@gmail.com> writes:
Show 8 quoted lines
> On Mon, Aug 12, 2013 at 3:37 PM, David Jeske <davidj@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".