Re: What's cooking in git.git (Feb 2012, #09; Sun, 26)
- From
Øyvind A. Holm <sunny@sunbase.org>
- Date
- Mar 1, 2012, 00:11 UTC
- Message-ID
- <CAA787rkZKxYk_+WGD7_EhqxouzT=nhUEG0nn8KpZLSJskKiJdA@mail.gmail.com>
- In-Reply-To
- <7vd390btrf.fsf@alter.siamese.dyndns.org>
On 27 February 2012 08:49, Junio C Hamano <gitster@pobox.com> wrote:
Show 10 quoted lines
> * 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