All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heba Waly <heba.waly@gmail.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Heba Waly via GitGitGadget <gitgitgadget@gmail.com>,
	Git List <git@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/1] doc: fix a typo in gitcore-tutorial.txt
Date: Wed, 8 Jan 2020 13:09:47 +1300	[thread overview]
Message-ID: <CACg5j24A+g3_MFQvurd1Esy1s6A8W4VkLEWZjiP5WXxcTvqr-A@mail.gmail.com> (raw)
In-Reply-To: <CAPig+cTv5SOxEjjVQ7QvqJ1WbZGbcXegcCP4d5CK+nSdJvkNdQ@mail.gmail.com>

On Wed, Jan 8, 2020 at 12:35 AM Eric Sunshine <sunshine@sunshineco.com> wrote:
>
>
> Calling this change a "typo fix" confuses reviewers since it's clearly
> not a mere typographical error. It looks instead as if you are
> recommending git-switch over git-checkout, so a reader would expect
> the commit message to justify that change rather than merely calling
> it a "typo fix". However, digging deeper, one finds that this is
> actually fixing an oversight from an earlier change which already
> updated this file to prefer git-switch over git-checkout.
>
> 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.

Looks like I overlooked this commit for its simplicity, I thought it
was too simple and self explanatory. I agree with you though.

Thanks,
Heba

  parent reply	other threads:[~2020-01-08  0:10 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 [this message]
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=CACg5j24A+g3_MFQvurd1Esy1s6A8W4VkLEWZjiP5WXxcTvqr-A@mail.gmail.com \
    --to=heba.waly@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.