aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKyle Meyer <kyle@kyleam.com>2021-02-06 13:06:29 -0500
committerKyle Meyer <kyle@kyleam.com>2021-02-07 12:36:52 -0500
commitba628c1f0851923b422e7e123c3398dfcc9a4d1d (patch)
treec8c8e55d2ef41bc347a51835561a12fc0a3bd2a4
parent5d908ac0e0e3b31eabc0f0bcccafdec5abfdfaf4 (diff)
downloadpiem-ba628c1f0851923b422e7e123c3398dfcc9a4d1d.tar.gz
manual: contributing: Mention range-diff
-rw-r--r--piem.texi7
1 files changed, 7 insertions, 0 deletions
diff --git a/piem.texi b/piem.texi
index ecd17e6..bb5c684 100644
--- a/piem.texi
+++ b/piem.texi
@@ -483,6 +483,13 @@ format-patch} or by configuring @code{format.useAutoBase}.
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
+option.
+
@end itemize