git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Andrew Kreimer <algonell@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Documentation/config: fix typos
Date: Mon, 23 Sep 2024 13:51:50 -0400	[thread overview]
Message-ID: <CAPig+cSZmKCwy_sFKPR-w+DjXeTJJec1BAM6wDXMyEMWhoAY6g@mail.gmail.com> (raw)
In-Reply-To: <20240923110343.12388-1-algonell@gmail.com>

On Mon, Sep 23, 2024 at 7:04 AM Andrew Kreimer <algonell@gmail.com> wrote:
> Fix typos in documentation.
>
> Signed-off-by: Andrew Kreimer <algonell@gmail.com>

Thanks. The changes in v2 of this series look fine.

In the future, to make life easier for reviewers, when rerolling a
patch series, please include a cover letter ("git format-patch
--cover-letter") and include the following in the cover letter:

* explain in your own words how the new version of the series differs
from the previous version

* provide a link to the cover-letter of the previous version (i.e.
https://lore.kernel.org/git/20240920082815.8192-1-algonell@gmail.com/)

* include a range-diff ("git format-patch --range-diff=") which
provides a mechanical representation of the differences between the
new version of the series and the previous version

Depending upon how dramatically the patch series changes from one
version to the next, the range-diff may end up being unreadable
gobbledygook, in which case you may instead want to include an
interdiff ("git format-patch --interdiff").

If you're rerolling just a single patch instead of a full patch
series, rather than including a cover letter, instead place the above
information in the commentary section of the patch (immediately below
the "---" line which follows your sign-off), and use "git format-patch
--range-diff" (or "--interdiff") to insert the mechanical differences
(which may appear in the commentary section or at the end of the
patch, depending upon which version of Git you're using).

  parent reply	other threads:[~2024-09-23 17:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-23 11:03 [PATCH v2 1/2] Documentation/config: fix typos Andrew Kreimer
2024-09-23 11:03 ` [PATCH v2 2/2] Documentation: " Andrew Kreimer
2024-09-23 17:51 ` Eric Sunshine [this message]
2024-09-23 17:59   ` [PATCH v2 1/2] Documentation/config: " Eric Sunshine
2024-09-23 20:01     ` Andrew Kreimer
2024-09-23 18:43   ` Kristoffer Haugsbakk
2024-09-23 19:05     ` Eric Sunshine
2024-09-23 19:13       ` Kristoffer Haugsbakk
2024-11-25 20:20         ` Kristoffer Haugsbakk

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=CAPig+cSZmKCwy_sFKPR-w+DjXeTJJec1BAM6wDXMyEMWhoAY6g@mail.gmail.com \
    --to=sunshine@sunshineco.com \
    --cc=algonell@gmail.com \
    --cc=git@vger.kernel.org \
    /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).