From: Junio C Hamano <gitster@pobox.com>
To: "Heba Waly via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Heba Waly <heba.waly@gmail.com>
Subject: Re: [PATCH v2 1/1] doc/gitcore-tutorial: fix prose to match example command
Date: Wed, 08 Jan 2020 08:57:53 -0800 [thread overview]
Message-ID: <xmqqr2093my6.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <0c75cd8f9727b10af6f6a804177e551ba0217abf.1578443496.git.gitgitgadget@gmail.com> (Heba Waly via GitGitGadget's message of "Wed, 08 Jan 2020 00:31:36 +0000")
"Heba Waly via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: Heba Waly <heba.waly@gmail.com>
>
> In 328c6cb853 (doc: promote "git switch", 2019-03-29), an example
> was changed to use "git switch" rather than "git checkout" but an
> instance of "git checkout" in the explanatory text preceding the
> example was overlooked. Fix this oversight.
>
> Signed-off-by: Heba Waly <heba.waly@gmail.com>
> ---
> Documentation/gitcore-tutorial.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt
> index f880d21dfb..c0b95256cc 100644
> --- a/Documentation/gitcore-tutorial.txt
> +++ b/Documentation/gitcore-tutorial.txt
> @@ -751,7 +751,7 @@ to it.
> ================================================
> If you make the decision to start your new branch at some
> other point in the history than the current `HEAD`, you can do so by
> -just telling 'git checkout' what the base of the checkout would be.
> +just telling 'git switch' what the base of the checkout would be.
> In other words, if you have an earlier tag or branch, you'd just do
>
> ------------
Thanks. The part before this paragraph does illustrate the use of
"switch", and we should talk about that command here, too.
prev parent reply other threads:[~2020-01-08 16:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 10:05 [PATCH 0/1] [Outreachy] doc: fix a typo in gitcore-tutorial.txt Heba Waly via GitGitGadget
2020-01-07 10:05 ` [PATCH 1/1] " Heba Waly via GitGitGadget
2020-01-07 11:35 ` Eric Sunshine
2020-01-07 19:58 ` Junio C Hamano
2020-01-08 0:09 ` Heba Waly
2020-01-08 0:31 ` [PATCH v2 0/1] [Outreachy] doc/gitcore-tutorial: fix prose to match example command Heba Waly via GitGitGadget
2020-01-08 0:31 ` [PATCH v2 1/1] " Heba Waly via GitGitGadget
2020-01-08 16:57 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqr2093my6.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=heba.waly@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).