From: Junio C Hamano Date: Thu, 3 Sep 2020 19:37:01 +0000 (-0700) Subject: Merge branch 'pw/rebase-i-more-options' X-Git-Tag: v2.29.0-rc0~107 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=9c31b19dd00981fcea435de1cd05eab179039a8d;p=thirdparty%2Fgit.git Merge branch 'pw/rebase-i-more-options' "git rebase -i" learns a bit more options. * pw/rebase-i-more-options: t3436: do not run git-merge-recursive in dashed form rebase: add --reset-author-date rebase -i: support --ignore-date rebase -i: support --committer-date-is-author-date am: stop exporting GIT_COMMITTER_DATE rebase -i: add --ignore-whitespace flag --- 9c31b19dd00981fcea435de1cd05eab179039a8d diff --cc Documentation/git-rebase.txt index 374d2486f7,1ee3bb4fac..e8df8d5214 --- a/Documentation/git-rebase.txt +++ b/Documentation/git-rebase.txt @@@ -455,12 -420,25 +455,27 @@@ If is given on the command l If your branch was based on but was rewound and your branch contains commits which were dropped, this option can be used with `--keep-base` in order to drop those commits from your branch. ++ +See also INCOMPATIBLE OPTIONS below. --ignore-whitespace:: + Ignore whitespace differences when trying to reconcile + differences. Currently, each backend implements an approximation of + this behavior: + + + apply backend: When applying a patch, ignore changes in whitespace in + context lines. Unfortunately, this means that if the "old" lines being + replaced by the patch differ only in whitespace from the existing + file, you will get a merge conflict instead of a successful patch + application. + + + merge backend: Treat lines with only whitespace changes as unchanged + when merging. Unfortunately, this means that any patch hunks that were + intended to modify whitespace and nothing else will be dropped, even + if the other side had no changes that conflicted. + --whitespace=