From: Jeff King <peff@peff.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>, git@vger.kernel.org
Subject: Re: Silent maintenance
Date: Sat, 14 Aug 2010 18:04:10 -0400 [thread overview]
Message-ID: <20100814220410.GA16592@coredump.intra.peff.net> (raw)
In-Reply-To: <AANLkTimLHand0g965TJmk=Y4Q+0uTFovZZRZXf9Fx4UB@mail.gmail.com>
On Sat, Aug 14, 2010 at 09:41:44PM +0000, Ævar Arnfjörð Bjarmason wrote:
> 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
next prev parent reply other threads:[~2010-08-14 22:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 13:11 Silent maintenance Enrico Weigelt
2010-08-14 13:26 ` Ævar Arnfjörð Bjarmason
2010-08-14 16:33 ` Valeo de Vries
2010-08-14 16:41 ` Ævar Arnfjörð Bjarmason
2010-08-14 21:05 ` Jonathan Nieder
2010-08-14 21:41 ` Ævar Arnfjörð Bjarmason
2010-08-14 22:04 ` Jeff King [this message]
2010-08-15 0:21 ` Ævar Arnfjörð Bjarmason
2010-08-15 13:12 ` Enrico Weigelt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100814220410.GA16592@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).