From: Tay Ray Chuan <rctay89@gmail.com>
To: git@vger.kernel.org
Cc: Miklos Vajna <vmiklos@frugalware.org>,
Nicolas Pitre <nico@fluxnic.net>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Junio C Hamano" <gitster@pobox.com>
Subject: [PATCH 0/4] clone: use --progress to mean -v
Date: Sat, 26 Dec 2009 01:12:02 +0800 [thread overview]
Message-ID: <1261761126-5784-1-git-send-email-rctay89@gmail.com> (raw)
In-Reply-To: 18831.46833.862.196815@hungover.brentg.com
This series makes git-clone follow the "argument convention" of
git-pack-objects, where the option --progress is used to force
reporting of reporting. This was previously done with -v/--verbose.
This in effect ensures a single consistent convention regarding
progress reporting for git commands. Having two conventions may
potentially confuse users.
On a related note, Brent wrote a patch a while back [1]. This series is
not as ambitious his and does not deal with the main git options. In
fact, only the last patch effects the titular change. If a consensus is
reached on this though, I don't rule out a separate patch/series to
set the convention at the main git level.
PS. If someone can enlighten me on the proper noun for the git
executable (I said "main git"), I would be very thankful.
PPS. Merry Christmas and happy holidays. :)
Tay Ray Chuan (4):
check stderr with isatty() instead of stdout when deciding to show
progress
git-clone.txt: reword description of progress behaviour
clone: set transport->verbose when -v/--verbose is used
clone: use --progress to force progress reporting
Documentation/git-clone.txt | 12 +++++++++---
builtin-clone.c | 6 ++++++
t/t5702-clone-options.sh | 3 ++-
transport-helper.c | 2 +-
transport.c | 2 +-
transport.h | 2 +-
6 files changed, 20 insertions(+), 7 deletions(-)
Footnotes:
[1] http://marc.info/?l=git&m=123415527432713
--
Cheers,
Ray Chuan
next prev parent reply other threads:[~2009-12-25 17:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 4:54 [PATCH/RFC] Add progress options Brent Goodrick
2009-12-25 17:12 ` Tay Ray Chuan [this message]
2009-12-25 17:12 ` [PATCH 1/4] check stderr with isatty() instead of stdout when deciding to show progress Tay Ray Chuan
2009-12-25 17:12 ` [PATCH 2/4] git-clone.txt: reword description of progress behaviour Tay Ray Chuan
2009-12-25 17:12 ` [PATCH 3/4] clone: set transport->verbose when -v/--verbose is used Tay Ray Chuan
2009-12-25 17:12 ` [PATCH 4/4] clone: use --progress to force progress reporting Tay Ray Chuan
2009-12-27 1:20 ` Miklos Vajna
2009-12-27 3:22 ` Tay Ray Chuan
2009-12-26 8:53 ` [PATCH 0/4] clone: use --progress to mean -v Johannes Schindelin
2009-12-27 3:27 ` Tay Ray Chuan
2009-12-29 1:30 ` Junio C Hamano
2009-12-29 3:06 ` Tay Ray Chuan
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=1261761126-5784-1-git-send-email-rctay89@gmail.com \
--to=rctay89@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nico@fluxnic.net \
--cc=vmiklos@frugalware.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).