git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nicolas Pitre <nico@cam.org>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	Albert Astals Cid <aacid@kde.org>,
	Pau Garcia i Quiles <pgquiles@elpauer.org>,
	git@vger.kernel.org
Subject: Re: [PATCH 3/3] transport: don't show push status if --quiet is given
Date: Wed, 5 Aug 2009 17:17:00 -0400	[thread overview]
Message-ID: <20090805211700.GA24697@coredump.intra.peff.net> (raw)
In-Reply-To: <7vws5ix9dz.fsf@alter.siamese.dyndns.org>

On Wed, Aug 05, 2009 at 02:01:44PM -0700, Junio C Hamano wrote:

> What I meant was that I'd still want to see the non-verbose part of
> print_push_status(), while suppressing the progress report.  That would
> make mails coming from the cron job much more pleasant to read.
> 
> If you somehow can automatically squelch progress without -q for an
> unattended invocation (e.g. cron jobs), then I wouldn't need to pass -q
> and everything will be good.  But if I have to pass -q in order to squelch
> progress, I do not want that same -q to automatically also mean "no status
> output", which is what your 3/3 is about, if I am reading the patch
> correctly.  That's all.

Hmm. Doesn't that already work? pack-objects checks isatty(2) already
before outputting progress, which means it should be suppressed when run
via cron (the original poster is seeing it, though, which maybe means
some crons allocate a terminal?).

But it sounds like git already does what you want; this extra "-q" would
really be more about shutting up the ref status. If you really wanted to
control them separately (e.g., because your isatty check is not
reliable), then maybe it should be split into "--quiet" and
"--no-progress"?

-Peff

  reply	other threads:[~2009-08-05 21:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-04 21:27 Making git push output quieter Albert Astals Cid
2009-08-04 22:20 ` Pau Garcia i Quiles
2009-08-05 19:13   ` Albert Astals Cid
2009-08-05 19:26     ` Shawn O. Pearce
2009-08-05 19:51       ` Nicolas Pitre
2009-08-05 20:19         ` Jeff King
2009-08-05 20:22           ` [RFC/PATCH 1/3] push: add --quiet flag Jeff King
2009-08-05 20:22           ` [PATCH 2/3] transport: pass "quiet" flag to pack-objects Jeff King
2009-08-05 20:23           ` [PATCH 3/3] transport: don't show push status if --quiet is given Jeff King
2009-08-05 20:27             ` Sverre Rabbelier
2009-08-05 20:29               ` Avery Pennarun
2009-08-05 20:30                 ` Sverre Rabbelier
2009-08-05 20:39             ` Junio C Hamano
2009-08-05 20:48               ` Jeff King
2009-08-05 21:01                 ` Junio C Hamano
2009-08-05 21:17                   ` Jeff King [this message]
2009-08-31 18:33                     ` Sebastian Pipping
2009-08-31 19:28                       ` Jeff King
2009-08-31 19:39                         ` Sebastian Pipping

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090805211700.GA24697@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=aacid@kde.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nico@cam.org \
    --cc=pgquiles@elpauer.org \
    --cc=spearce@spearce.org \
    /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.
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 NNTP newsgroup(s).