git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v2 03/10] Documentation/git-push: put --quiet before --verbose

From
Tay Ray Chuan <rctay89@gmail.com>
Date
Feb 24, 2010, 12:50 UTC
Message-ID
<1267015829-5344-4-git-send-email-rctay89@gmail.com>
In-Reply-To
<1267015829-5344-1-git-send-email-rctay89@gmail.com>
Signed-off-by: Tay Ray Chuan <rctay89@gmail.com>
---
 Documentation/git-push.txt |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
index 49b6bd9..ddb78eb 100644
--- a/Documentation/git-push.txt
+++ b/Documentation/git-push.txt
@@ -146,15 +146,15 @@ useful if you write an alias or script around 'git push'.
 	receiver share many of the same objects in common. The default is
 	\--thin.
 
--v::
---verbose::
-	Run verbosely.
-
 -q::
 --quiet::
 	Suppress all output, including the listing of updated refs,
 	unless an error occurs.
 
+-v::
+--verbose::
+	Run verbosely.
+
 include::urls-remotes.txt[]
 
 OUTPUT
-- 
1.7.0.20.gcb44ed
Previous: Tay Ray ChuanNext: Tay Ray Chuan
Message 4 of 11 in “teach --progress to transport-related builtins”
  1. 00/10 teach --progress to transport-related builtinsTay Ray Chuan, Feb 24, 2010
  2. 01/10 Documentation/git-clone: mention progress in -vTay Ray Chuan, Feb 24, 2010
  3. 02/10 Documentation/git-pull: put verbosity options before merge/fetch onesTay Ray Chuan, Feb 24, 2010
  4. 03/10 Documentation/git-push: put --quiet before --verboseTay Ray Chuan, Feb 24, 2010
  5. 04/10 fetch: refactor verbosity option handling into transport.[ch]Tay Ray Chuan, Feb 24, 2010
  6. 05/10 push: support multiple levels of verbosityTay Ray Chuan, Feb 24, 2010
  7. 06/10 clone: support multiple levels of verbosityTay Ray Chuan, Feb 24, 2010
  8. 07/10 transport->progress: use flag authoritativelyTay Ray Chuan, Feb 24, 2010
  9. 08/10 push: learn --progressTay Ray Chuan, Feb 24, 2010
  10. 09/10 fetch and pull: learn --progressTay Ray Chuan, Feb 24, 2010
  11. 10/10 transport: update flags to be in running orderTay Ray Chuan, Feb 24, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.