[prev in list] [next in list] [prev in thread] [next in thread] 

List:       git
Subject:    Re: [PATCH] Documentation: restore a space in unpack-objects usage
From:       Junio C Hamano <gitster () pobox ! com>
Date:       2013-10-31 22:09:54
Message-ID: xmqqy5592itp.fsf () gitster ! dls ! corp ! google ! com
[Download RAW message or body]

Vivien Didelot <vivien.didelot@savoirfairelinux.com> writes:

> The commit 87b7b84 removed a space in the unpack-objects usage, which
> makes the synopsis a bit confusing. This patch simply restores it.
>
> Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
> ---
>  Documentation/git-unpack-objects.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/git-unpack-objects.txt b/Documentation/git-unpack-objects.txt
> index ff23494..817788e 100644
> --- a/Documentation/git-unpack-objects.txt
> +++ b/Documentation/git-unpack-objects.txt
> @@ -9,7 +9,7 @@ git-unpack-objects - Unpack objects from a packed archive
>  SYNOPSIS
>  --------
>  [verse]
> -'git unpack-objects' [-n] [-q] [-r] [--strict] <pack-file
> +'git unpack-objects' [-n] [-q] [-r] [--strict] < pack-file

Thanks; that change was indeed not intended.

Looking at synopsis sections for other commands that take their
input from the standard input (e.g. "git check-attr"), I think
we should make it clear that "pack-file" is not to be spelled as-is
at the same time, i.e.

	'git unpack-objects' [-n] [-q] [-r] [--strict] < <pack-file>

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]