discussion and development of piem
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: piem@inbox.kyleam.com
Subject: [PATCH 2/3] manual: contributing: Mention range-diff
Date: Sat,  6 Feb 2021 13:06:29 -0500	[thread overview]
Message-ID: <20210206180630.3676-3-kyle@kyleam.com> (raw)
In-Reply-To: <20210206180630.3676-1-kyle@kyleam.com>

 piem.texi | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/piem.texi b/piem.texi
index ecd17e6..bb5c684 100644
--- a/piem.texi
+++ b/piem.texi
@@ -483,6 +483,13 @@ Contributing
 In general, prefer to keep iterations of a patch series in the same
 thread, labeling rerolls with an appropriate version.
+@item Consider adding a range-diff to the cover letter of rerolls.
+For a multi-patch series, @code{git range-diff} can often provide a nice
+overview of the changes between the previous and last iteration.  Note
+that @code{git format-patch} has a @code{--range-diff} convenience
 @end itemize

  parent reply	other threads:[~2021-02-06 18:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-06 18:06 [PATCH 0/3] manual: Point to range-diff and related projects Kyle Meyer
2021-02-06 18:06 ` [PATCH 1/3] manual: contributing: Remove some unnecessary bits Kyle Meyer
2021-02-06 18:06 ` Kyle Meyer [this message]
2021-02-06 18:06 ` [PATCH 3/3] manual: Add a "Related projects and tools" section Kyle Meyer

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:

  List information: https://git.kyleam.com/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210206180630.3676-3-kyle@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.com \


* 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


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).