The value is not a percentage that ranges from 0 to 100, so stop
referring to it as `percent`; instead follow the lead of the `git
range-diff` documentation and call it `factor`.
Signed-off-by: Eric Sunshine <redacted>
---
This is a sibling to Junio's patch[1].
[1]: https://lore.kernel.org/git/xmqqo7x9ch7n.fsf_-_@gitster.g/ (local)
Documentation/git-format-patch.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt
index be797d7a28..e06475abcd 100644
--- a/Documentation/git-format-patch.txt
+++ b/Documentation/git-format-patch.txt
@@ -27,7 +27,7 @@ SYNOPSIS
[--[no-]encode-email-headers]
[--no-notes | --notes[=<ref>]]
[--interdiff=<previous>]
- [--range-diff=<previous> [--creation-factor=<percent>]]
+ [--range-diff=<previous> [--creation-factor=<factor>]]
[--filename-max-length=<n>]
[--progress]
[<common diff options>]
@@ -321,7 +321,7 @@ product of `format-patch` is generated, and they are not passed to
the underlying `range-diff` machinery used to generate the cover-letter
material (this may change in the future).
---creation-factor=<percent>::
+--creation-factor=<factor>::
Used with `--range-diff`, tweak the heuristic which matches up commits
between the previous and current series of patches by adjusting the
creation/deletion cost fudge factor. See linkgit:git-range-diff[1])
--
2.37.1.550.gb06344481a