On 27 February 2012 08:49, Junio C Hamano <gitster@xxxxxxxxx> wrote: > * cb/fsck-squelch-dangling (2012-02-26) 1 commit > - fsck: do not print dangling objects by default > > Introduces "fsck --dangling" and removes the output for dangling objects > from the default output. > > I personally do not think it is worth risking backward compatibility in > the way this patch implements the squelching of the output. An approach > to add --no-dangling option without changing the default would be OK, > though. Agree. I use this functionality a lot, and this change would break a script I use to restore dangling commits. There's probably some (dirty) way around it, but I'd prefer if the backwards compatibility is retained. BTW, the script I use is located at <https://github.com/sunny256/utils/blob/master/git-dangling> and I find it quite useful. Do you think it could be a contrib/ candidate? Cheers, Øyvind -- 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