summaryrefslogtreecommitdiffstats
path: root/git-range-diff.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2018-11-18 21:44:26 +0900
committerJunio C Hamano <gitster@pobox.com>2018-11-18 21:44:26 +0900
commit69bb2b541d6b878a1bf72199f90b2e5dba140a56 (patch)
tree99cafeef63a6ff03379d08391072bf41fccb21e6 /git-range-diff.txt
parent06ce83b0f83d238e1676b4adb708f142ab2f9cab (diff)
downloadgit-htmldocs-69bb2b541d6b878a1bf72199f90b2e5dba140a56.tar.gz
Autogenerated HTML docs for v2.20.0-rc0
Diffstat (limited to 'git-range-diff.txt')
-rw-r--r--git-range-diff.txt17
1 files changed, 17 insertions, 0 deletions
diff --git a/git-range-diff.txt b/git-range-diff.txt
index f693930fd..8a6ea2c6c 100644
--- a/git-range-diff.txt
+++ b/git-range-diff.txt
@@ -78,6 +78,23 @@ between patches", i.e. to compare the author, commit message and diff of
corresponding old/new commits. There is currently no means to tweak the
diff options passed to `git log` when generating those patches.
+OUTPUT STABILITY
+----------------
+
+The output of the `range-diff` command is subject to change. It is
+intended to be human-readable porcelain output, not something that can
+be used across versions of Git to get a textually stable `range-diff`
+(as opposed to something like the `--stable` option to
+linkgit:git-patch-id[1]). There's also no equivalent of
+linkgit:git-apply[1] for `range-diff`, the output is not intended to
+be machine-readable.
+
+This is particularly true when passing in diff options. Currently some
+options like `--stat` can, as an emergent effect, produce output
+that's quite useless in the context of `range-diff`. Future versions
+of `range-diff` may learn to interpret such options in a manner
+specific to `range-diff` (e.g. for `--stat` producing human-readable
+output which summarizes how the diffstat changed).
CONFIGURATION
-------------