From: Jeff King <peff@peff.net>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Sebastian Pipping <webmaster@hartwork.org>,
git@vger.kernel.org
Subject: Re: [PATCH] Document git push -q
Date: Mon, 19 Oct 2009 00:01:19 -0400 [thread overview]
Message-ID: <20091019040119.GA7170@coredump.intra.peff.net> (raw)
In-Reply-To: <20091018235240.GU6115@genesis.frugalware.org>
On Mon, Oct 19, 2009 at 01:52:40AM +0200, Miklos Vajna wrote:
> diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
> index ba6a8a2..beb3422 100644
> --- a/Documentation/git-push.txt
> +++ b/Documentation/git-push.txt
> @@ -138,6 +138,12 @@ useful if you write an alias or script around 'git-push'.
> --verbose::
> Run verbosely.
>
> +-q::
> +--quiet::
> + Some transports produce output even without `--verbose` turned
> + on. This provides a way to tell them to be more quiet (whereas
> + simply redirecting might lose error messages).
> +
Thanks, though two complaints:
1. This is not just about "some transports". Some of the quieted code
is in transport_push, so hopefully it applies to all transports
once they follow that code path (though we also pass the quiet flag
on to pack-objects, so that part is about "some transports".
2. Maybe it would be more helpful to the user to describe what is
shown and what is not. I think we want to claim to suppress all
non-error output (since that was the intent of the recent patches).
If that is not true for some transport, then we need to fix passing
--quiet to that transport.
...Ah, I see your confusion. You read the log for afdeeb00, but there
were some follow-on patches that impacted others part of push. :)
So maybe this instead:
-- >8 --
Subject: [PATCH] document push's new quiet option
Signed-off-by: Jeff King <peff@peff.net>
---
Documentation/git-push.txt | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
index ba6a8a2..37c8895 100644
--- a/Documentation/git-push.txt
+++ b/Documentation/git-push.txt
@@ -138,6 +138,11 @@ useful if you write an alias or script around 'git-push'.
--verbose::
Run verbosely.
+-q::
+--quiet::
+ Suppress all output, including the listing of updated refs,
+ unless an error occurs.
+
include::urls-remotes.txt[]
OUTPUT
--
1.6.5.1.121.g65c47
next prev parent reply other threads:[~2009-10-19 4:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-11 8:40 [ANNOUNCE] GIT 1.6.5 Junio C Hamano
2009-10-11 16:30 ` Steven Noonan
2009-10-11 16:30 ` Steven Noonan
2009-10-11 18:47 ` Junio C Hamano
2009-10-11 18:57 ` Steven Noonan
2009-10-14 22:11 ` Jakub Narebski
2009-10-18 17:05 ` Sebastian Pipping
2009-10-18 23:52 ` [PATCH] Document git push -q Miklos Vajna
2009-10-19 2:54 ` [PATCH] git push: remove incomplete options list from help text Nanako Shiraishi
2009-10-19 3:13 ` Junio C Hamano
2009-10-19 3:57 ` [PATCH] git push: say that --tag can't be used with --all or --mirror in " Nanako Shiraishi
2009-10-19 4:14 ` Jeff King
2009-10-21 14:42 ` Jeff King
2009-10-21 21:21 ` Nanako Shiraishi
2009-10-19 4:10 ` [PATCH] git push: remove incomplete options list from " Jeff King
2009-10-19 5:41 ` Junio C Hamano
2009-10-19 4:01 ` Jeff King [this message]
2009-10-19 5:58 ` [PATCH] Document git push -q Junio C Hamano
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=20091019040119.GA7170@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=vmiklos@frugalware.org \
--cc=webmaster@hartwork.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).