From: Johannes Sixt <j6t@kdbg.org>
To: Edmundo Carmona Antoranz <eantoranz@gmail.com>
Cc: git@vger.kernel.org, peff@peff.net, max@max630.net
Subject: Re: [PATCH v2] blame: add support for --[no-]progress option
Date: Sun, 22 Nov 2015 20:58:49 +0100 [thread overview]
Message-ID: <56521E79.4080709@kdbg.org> (raw)
In-Reply-To: <1448208133-29430-1-git-send-email-eantoranz@gmail.com>
Am 22.11.2015 um 17:02 schrieb Edmundo Carmona Antoranz:
> Will also affect annotate
>
> Signed-off-by: Edmundo Carmona Antoranz <eantoranz@gmail.com>
> ---
> Documentation/blame-options.txt | 7 +++++++
> Documentation/git-blame.txt | 9 ++++++++-
> builtin/blame.c | 25 +++++++++++++++++++++++--
> 3 files changed, 38 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/blame-options.txt b/Documentation/blame-options.txt
> index 760eab7..43f4f08 100644
> --- a/Documentation/blame-options.txt
> +++ b/Documentation/blame-options.txt
> @@ -69,6 +69,13 @@ include::line-range-format.txt[]
> iso format is used. For supported values, see the discussion
> of the --date option at linkgit:git-log[1].
>
> +--[no-]progress::
> + Progress status is reported on the standard error stream
> + by default when it is attached to a terminal. This flag
> + enables progress reporting even if not attached to a
> + terminal.
> +
> +
> -M|<num>|::
> Detect moved or copied lines within a file. When a commit
> moves or copies a block of lines (e.g. the original file
> diff --git a/Documentation/git-blame.txt b/Documentation/git-blame.txt
> index e6e947c..2e63397 100644
> --- a/Documentation/git-blame.txt
> +++ b/Documentation/git-blame.txt
> @@ -10,7 +10,8 @@ SYNOPSIS
> [verse]
> 'git blame' [-c] [-b] [-l] [--root] [-t] [-f] [-n] [-s] [-e] [-p] [-w] [--incremental]
> [-L <range>] [-S <revs-file>] [-M] [-C] [-C] [-C] [--since=<date>]
> - [--abbrev=<n>] [<rev> | --contents <file> | --reverse <rev>] [--] <file>
> + [--[no-]progress] [--abbrev=<n>] [<rev> | --contents <file> | --reverse <rev>]
> + [--] <file>
You add the option to to the synopsis of git-blame.txt, but not to
git-annotate.txt.
>
> DESCRIPTION
> -----------
> @@ -88,6 +89,12 @@ include::blame-options.txt[]
> abbreviated object name, use <n>+1 digits. Note that 1 column
> is used for a caret to mark the boundary commit.
>
> +--[no-]progress::
> + Progress status is reported on the standard error stream
> + by default when it is attached to a terminal. This flag
> + enables progress reporting even if not attached to a
> + terminal.
> +
Any particular reason you add this text twice? As can be seen on the
hunk header, git-blame.txt includes blame-options.txt.
-- Hannes
next prev parent reply other threads:[~2015-11-22 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 16:02 [PATCH v2] blame: add support for --[no-]progress option Edmundo Carmona Antoranz
2015-11-22 19:58 ` Johannes Sixt [this message]
2015-11-22 20:28 ` Edmundo Carmona Antoranz
2015-11-23 2:08 ` Junio C Hamano
2015-11-23 2:47 ` Edmundo Carmona Antoranz
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=56521E79.4080709@kdbg.org \
--to=j6t@kdbg.org \
--cc=eantoranz@gmail.com \
--cc=git@vger.kernel.org \
--cc=max@max630.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.