From: Junio C Hamano <gitster@pobox.com>
To: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: restore a space in unpack-objects usage
Date: Thu, 31 Oct 2013 15:09:54 -0700 [thread overview]
Message-ID: <xmqqy5592itp.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1383255671-12784-1-git-send-email-vivien.didelot@savoirfairelinux.com> (Vivien Didelot's message of "Thu, 31 Oct 2013 17:41:11 -0400")
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>
next prev parent reply other threads:[~2013-10-31 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 21:41 [PATCH] Documentation: restore a space in unpack-objects usage Vivien Didelot
2013-10-31 22:09 ` Junio C Hamano [this message]
2013-11-01 15:42 ` [PATCH] Documentation: "pack-file" is not literal in unpack-objects Vivien Didelot
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=xmqqy5592itp.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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 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).