From: Petr Baudis <pasky@suse•cz>
To: Nicolas Pitre <nico@fluxnic•net>
Cc: Junio C Hamano <gitster@pobox•com>, Jeff King <peff@peff•net>,
bill lam <cbill.lam@gmail•com>, git <git@vger•kernel.org>
Subject: Re: [PATCH] pack-objects: split implications of --all-progress from progress activation
Date: Mon, 23 Nov 2009 19:12:06 +0100 [thread overview]
Message-ID: <20091123181206.GD26996@machine.or.cz> (raw)
In-Reply-To: <alpine.LFD.2.00.0911231221320.2059@xanadu.home>
On Mon, Nov 23, 2009 at 12:43:50PM -0500, Nicolas Pitre wrote:
> Currently the --all-progress flag is used to use force progress display
> during the writing object phase even if output goes to stdout which is
> primarily the case during a push operation. This has the unfortunate
> side effect of forcing progress display even if stderr is not a
> terminal.
>
> Let's introduce the --all-progress-implied argument which has the same
> intent except for actually forcing the activation of any progress
> display. With this, progress display will be automatically inhibited
> whenever stderr is not a terminal, or full progress display will be
> included otherwise. This should let people use 'git push' within a cron
> job without filling their logs with useless percentage displays.
>
> Signed-off-by: Nicolas Pitre <nico@fluxnic•net>
Ok, but what is currently the way to force the old behaviour? I believe
that should be also part of the commit message.
Naive deduction fails:
$ git remote update --progress
error: unknown option `progress'
Thanks,
--
Petr "Pasky" Baudis
A lot of people have my books on their bookshelves.
That's the problem, they need to read them. -- Don Knuth
next prev parent reply other threads:[~2009-11-23 18:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 14:53 how to suppress progress percentage in git-push bill lam
2009-11-23 15:00 ` Jeff King
2009-11-23 15:50 ` Petr Baudis
2009-11-23 16:43 ` Jeff King
2009-11-23 17:05 ` Petr Baudis
2009-11-23 19:28 ` Jeff King
2009-11-23 17:43 ` [PATCH] pack-objects: split implications of --all-progress from progress activation Nicolas Pitre
2009-11-23 18:12 ` Petr Baudis [this message]
2009-11-23 18:27 ` Nicolas Pitre
2009-11-23 19:04 ` Petr Baudis
2009-11-23 19:32 ` Jeff King
2009-11-23 16:56 ` how to suppress progress percentage in git-push Nicolas Pitre
2009-11-23 19:25 ` Jeff King
2009-11-23 19:40 ` Nicolas Pitre
2009-11-24 1:13 ` bill lam
2009-11-24 3:07 ` Jeff King
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=20091123181206.GD26996@machine.or.cz \
--to=pasky@suse$(echo .)cz \
--cc=cbill.lam@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=nico@fluxnic$(echo .)net \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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