Re: Silent maintenance

From: Jeff King <peff@peff.net>
Date: Aug 14, 2010, 22:04 UTC
Message-ID: <20100814220410.GA16592@coredump.intra.peff.net>
In-Reply-To: <AANLkTimLHand0g965TJmk=Y4Q+0uTFovZZRZXf9Fx4UB@mail.gmail.com>

On Sat, Aug 14, 2010 at 09:41:44PM +0000, Ævar Arnfjörð Bjarmason wrote:

Show 10 quoted lines

> On Sat, Aug 14, 2010 at 21:05, Jonathan Nieder <jrnieder@gmail.com> wrote:
> > Enrico Weigelt wrote:
> >
> >> are there some flags to make the maintenance commands like
> >> git-repack and git-gc silent, so they only output errors ?
> >
> > Does --quiet work?  If not, patches would be welcome.
> 
> I intentionally neglected to mention that. That inevitably leads to
> cases where something fails, but you didn't record the output.

I'm confused. Isn't the point of quiet to silence all of the cruft, and leave only actual errors?

  $ git gc
  Counting objects: 128, done.
  Compressing objects: 100% (49/49), done.
  Writing objects: 100% (128/128), done.
  Total 128 (delta 71), reused 121 (delta 68)

  $ git gc --quiet

  $ chmod -w .git/objects/pack
  $ git gc --quiet
  fatal: Unable to create temporary file: Permission denied
  error: failed to run repack

Isn't that what the OP wanted?

> cronjob(1) will consume all the output, and either print it all or
> nothing, depending on the exit code of the program it's running.

That is a good solution for broken programs that have no "print only errors" mode, but I don't think git is one of those (and if it is, we should fix it).

-Peff