git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Heba Waly via GitGitGadget <gitgitgadget@gmail.com>,
	Git List <git@vger.kernel.org>, Heba Waly <heba.waly@gmail.com>
Subject: Re: [PATCH 1/1] doc: fix a typo in gitcore-tutorial.txt
Date: Tue, 07 Jan 2020 11:58:08 -0800	[thread overview]
Message-ID: <xmqq36cr599r.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAPig+cTv5SOxEjjVQ7QvqJ1WbZGbcXegcCP4d5CK+nSdJvkNdQ@mail.gmail.com> (Eric Sunshine's message of "Tue, 7 Jan 2020 06:35:23 -0500")

Eric Sunshine <sunshine@sunshineco.com> writes:

> To save reviewers the time and effort of having to figure all this
> out, use the commit message to explain the situation. For example, you
> might say:
>
>     doc/gitcore-tutorial: fix prose to match example command
>
>     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.

Thanks for a ncie educational session ;-)

  reply	other threads:[~2020-01-07 19: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 [this message]
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

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=xmqq36cr599r.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=heba.waly@gmail.com \
    --cc=sunshine@sunshineco.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).