Re: [PATCH] fsck: do not print dangling objects by default

From: Clemens Buchacher <drizzd@aon.at>
Date: Feb 27, 2012, 22:18 UTC
Message-ID: <20120227221820.GA1194@ecki>
In-Reply-To: <20120227213304.GB19779@sigill.intra.peff.net>

On Mon, Feb 27, 2012 at 04:33:04PM -0500, Jeff King wrote:

Show 14 quoted lines

> On Mon, Feb 27, 2012 at 10:13:16PM +0100, Clemens Buchacher wrote:
> 
> > > Yes, that was certainly part of my pros-and-cons analysis.  If you run
> > > "git fsck" without "--no-dangling" without reading the manual, you may
> > > get confused, but that is *not* the primary audience.
> > 
> > It is not my only concern that users might be confused. I believe the
> > command prints a lot of useless messages, which is by itself a UI
> > deficiency. But even worse, those numerous messages tend to hide an
> > actual problem in a long scrollback buffer. Sometimes my scrollback
> > buffer is not even large enough and I have to re-run fsck (which is not
> > exactly a fast command), just so I can grep out the dangling blobs.
> 
> Yeah, but doesn't adding "--no-dangling" solve that issue?

I can just as well use grep -v ^dangling.