All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Štěpán Němec" <stepnem@gmail.com>
To: Bert Wesarg <bert.wesarg@googlemail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] Documentation: update-index: -z applies also to --index-info
Date: Thu, 07 Oct 2010 20:33:58 +0200	[thread overview]
Message-ID: <87wrptua21.fsf@gmail.com> (raw)
In-Reply-To: <d3f7e6795adeccbf7746547842d6b65732d568eb.1286457739.git.bert.wesarg@googlemail.com> (Bert Wesarg's message of "Thu, 7 Oct 2010 15:23:17 +0200")

Bert Wesarg <bert.wesarg@googlemail.com> writes:

> Also mention, that --stdin and --index-info needs to be the last
> option supplied and indicate this in the usage string.
>
> Signed-off-by: Bert Wesarg <bert.wesarg@googlemail.com>
>
> ---
>
> We may like the usage string like this:
>
> [[-z] --stdin | --index-info]

Yeah, that'd be definitely better IMO.

Also the usage string in builtin/update-index.c should be updated to the
same effect.

There is actually at least one more problem with the current SYNOPSIS of
`update-index'. Obviously the `*' on the third line of the Asciidoc
source makes the whole `--cacheinfo' line disappear and the rest bold
(cf. e.g. the result at
<http://www.kernel.org/pub/software/scm/git/docs/git-update-index.html>).

I guess using `...' instead of the asterisks (also on the last line,
i.e. [<file>...], not [<file>]*) would both fix the problem and at the
same time make it more consistent with other man pages.

> to make it also clear, that -z applies only to --stdin or --index-only.
> ---
>  Documentation/git-update-index.txt |   14 ++++++++------
>  1 files changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/git-update-index.txt
> b/Documentation/git-update-index.txt
> index 74d1d49..4441d7c 100644 Documentation/git-update-index.txt
> --- a/Documentation/git-update-index.txt
> +++ b/Documentation/git-update-index.txt
> @@ -18,8 +18,9 @@ SYNOPSIS
>  	     [--skip-worktree | --no-skip-worktree]
>  	     [--ignore-submodules]
>  	     [--really-refresh] [--unresolve] [--again | -g]
> -	     [--info-only] [--index-info]
> -	     [-z] [--stdin]
> +	     [--info-only]
> +	     [-z]
> +	     [--stdin] [--index-info]
>  	     [--verbose]
>  	     [--] [<file>]*

Shouldn't `--verbose' be also moved before the must-be-last options?

> @@ -72,7 +73,7 @@ OPTIONS
>  	Directly insert the specified info into the index.
>  
>  --index-info::
> -        Read index information from stdin.
> +        Read index information from stdin (Must be last option).

I'm not a native speaker myself, but I suspect "must be THE last option"
is more correct (including the lower-case `m' :-)).

>  --chmod=(+|-)x::
>          Set the execute permissions on the updated files.
> @@ -138,14 +139,15 @@ you will need to handle the situation manually.
>  --stdin::
>  	Instead of taking list of paths from the command line,
>  	read list of paths from the standard input.  Paths are
> -	separated by LF (i.e. one path per line) by default.
> +	separated by LF (i.e. one path per line) by default
> +	(Must be last option).

(same here)

>  
>  --verbose::
>          Report what is being added and removed from index.
>  
>  -z::
> -	Only meaningful with `--stdin`; paths are separated with
> -	NUL character instead of LF.
> +	Only meaningful with `--stdin` or `--index-info`; paths are
> +	separated with NUL character instead of LF.
>  
>  \--::
>  	Do not interpret any more arguments as options.

Thanks,

Štěpán

  reply	other threads:[~2010-10-07 18:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07 13:23 [PATCH] Documentation: update-index: -z applies also to --index-info Bert Wesarg
2010-10-07 18:33 ` Štěpán Němec [this message]
2010-10-07 18:52   ` Bert Wesarg
2010-10-07 18:55     ` Bert Wesarg
2010-10-07 19:15       ` Jonathan Nieder
2010-10-07 19:27         ` Štěpán Němec
2010-10-07 18:59     ` Bert Wesarg
2010-10-07 19:36       ` Štěpán Němec
2010-10-07 19:39         ` Bert Wesarg
2010-10-07 19:39           ` Bert Wesarg
2010-10-08  2:49             ` Junio C Hamano
2010-10-08  6:47               ` Bert Wesarg
2010-10-08  6:50                 ` Bert Wesarg

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=87wrptua21.fsf@gmail.com \
    --to=stepnem@gmail.com \
    --cc=bert.wesarg@googlemail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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.