git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tay Ray Chuan <rctay89@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Cc: "Junio C Hamano" <gitster@pobox.com>, "Jeff King" <peff@peff.net>,
	"Sebastian Thiel" <byronimo@googlemail.com>
Subject: [PATCH v2 00/10] teach --progress to transport-related builtins
Date: Wed, 24 Feb 2010 20:50:19 +0800	[thread overview]
Message-ID: <1267015829-5344-1-git-send-email-rctay89@gmail.com> (raw)

This patch series adds --progress to:

  - git-fetch
  - git-pull
  - git-push

Changes from v1:
  - rebased on git/next and resolved a conflict with the recent
    refactoring of print_push_status() in transports.

  - add a new patch for git-clone's documentation that mentions
    the effect of the -v/--verbose option on progress reporting.

    This should have been done with 5a518ad (clone: use --progress to
    force progress reporting), as per Miklos's suggestion
    (<20091227012032.GE25474@genesis.frugalware.org>).

  - put verbosity options (-v and -q) in a common area for the
    documentation for git-pull, as per Junio's suggestion
    (<7vhbpe5jvo.fsf@alter.siamese.dyndns.org>).

  - teach --progress to git-fetch and git-pull in one patch instead of
    two previously; after all, git-pull is a wrapper of git-fetch.

Contents:

[PATCH v2 01/10] Documentation/git-clone: mention progress in -v
[PATCH v2 02/10] Documentation/git-pull: put verbosity options before merge/fetch ones
[PATCH v2 03/10] Documentation/git-push: put --quiet before --verbose
[PATCH v2 04/10] fetch: refactor verbosity option handling into transport.[ch]
[PATCH v2 05/10] push: support multiple levels of verbosity
[PATCH v2 06/10] clone: support multiple levels of verbosity
[PATCH v2 07/10] transport->progress: use flag authoritatively
[PATCH v2 08/10] push: learn --progress
[PATCH v2 09/10] fetch and pull: learn --progress
[PATCH v2 10/10] transport: update flags to be in running order

 Documentation/fetch-options.txt |    9 ++++++++-
 Documentation/git-clone.txt     |    3 ++-
 Documentation/git-pull.txt      |   10 ++++++++++
 Documentation/git-push.txt      |   15 +++++++++++----
 Documentation/merge-options.txt |    2 ++
 builtin-clone.c                 |   19 ++++++-------------
 builtin-fetch.c                 |    7 +++----
 builtin-push.c                  |   11 ++++++++---
 git-pull.sh                     |    6 ++++--
 transport-helper.c              |    4 +---
 transport.c                     |   31 ++++++++++++++++++++++++++-----
 transport.h                     |   15 ++++++++++-----
 12 files changed, 91 insertions(+), 41 deletions(-)

             reply	other threads:[~2010-02-24 12:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 12:50 Tay Ray Chuan [this message]
2010-02-24 12:50 ` [PATCH v2 01/10] Documentation/git-clone: mention progress in -v Tay Ray Chuan
2010-02-24 12:50 ` [PATCH v2 02/10] Documentation/git-pull: put verbosity options before merge/fetch ones Tay Ray Chuan
2010-02-24 12:50 ` [PATCH v2 03/10] Documentation/git-push: put --quiet before --verbose Tay Ray Chuan
2010-02-24 12:50 ` [PATCH v2 04/10] fetch: refactor verbosity option handling into transport.[ch] Tay Ray Chuan
2010-02-24 12:50 ` [PATCH v2 05/10] push: support multiple levels of verbosity Tay Ray Chuan
2010-02-24 12:50 ` [PATCH v2 06/10] clone: " Tay Ray Chuan
2010-02-24 12:50 ` [PATCH v2 07/10] transport->progress: use flag authoritatively Tay Ray Chuan
2010-02-24 12:50 ` [PATCH v2 08/10] push: learn --progress Tay Ray Chuan
2010-02-24 12:50 ` [PATCH v2 09/10] fetch and pull: " Tay Ray Chuan
2010-02-24 12:50 ` [PATCH v2 10/10] transport: update flags to be in running order 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=1267015829-5344-1-git-send-email-rctay89@gmail.com \
    --to=rctay89@gmail.com \
    --cc=byronimo@googlemail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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).