From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org, Casey Rodarmor <casey@rodarmor.com>
Subject: Re: [PATCH] Documentation: correctly spell git worktree --detach
Date: Wed, 22 Feb 2017 09:50:45 -0800 [thread overview]
Message-ID: <xmqq7f4icdxm.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170222123442.923694-1-sandals@crustytoothpaste.net> (brian m. carlson's message of "Wed, 22 Feb 2017 12:34:42 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> The option is “--detach”, but we accidentally spelled it “--detached” at
> one point in the man page.
>
> Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
> Reported-by: Casey Rodarmor <casey@rodarmor.com>
> ---
Thanks, both.
> Documentation/git-worktree.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/git-worktree.txt b/Documentation/git-worktree.txt
> index e257c19ebe..553cf8413f 100644
> --- a/Documentation/git-worktree.txt
> +++ b/Documentation/git-worktree.txt
> @@ -52,7 +52,7 @@ is linked to the current repository, sharing everything except working
> directory specific files such as HEAD, index, etc. `-` may also be
> specified as `<branch>`; it is synonymous with `@{-1}`.
> +
> -If `<branch>` is omitted and neither `-b` nor `-B` nor `--detached` used,
> +If `<branch>` is omitted and neither `-b` nor `-B` nor `--detach` used,
> then, as a convenience, a new branch based at HEAD is created automatically,
> as if `-b $(basename <path>)` was specified.
>
prev parent reply other threads:[~2017-02-22 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANLPe+NVs9sJ7XQqvMabPBLg3DxS2Fyrrg3AzvZPBoWTPpnFzQ@mail.gmail.com>
2017-02-22 0:52 ` Fwd: Typo in worktree man page Casey Rodarmor
2017-02-22 12:32 ` brian m. carlson
2017-02-22 12:34 ` [PATCH] Documentation: correctly spell git worktree --detach brian m. carlson
2017-02-22 17:50 ` Junio C Hamano [this message]
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=xmqq7f4icdxm.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=casey@rodarmor.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.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