From: Elijah Newren Date: Tue, 07 Apr 2020 15:16:09 GMT Subject: Re: [PATCH 1/6] Revert "Revert "Merge branch 'ra/rebase-i-more-options'"" Message-ID: In-Reply-To: <20200407141125.30872-2-phillip.wood123@gmail.com> On Tue, Apr 7, 2020 at 7:11 AM Phillip Wood wrote: > > From: Phillip Wood > > This reverts commit 4d924528d8bfe947abfc54ee9bd3892ab509c8cd. > > This is being reverted to enable some fixups for > ra/rebase-i-more-options to be built on this commit. This makes sense to me, but it will be only the second 'Revert "Revert..."' commit in all of git.git and I'm curious if Junio will be unhappy with it. > --- > Documentation/git-rebase.txt | 27 ++++- > builtin/rebase.c | 49 ++++++-- > sequencer.c | 141 ++++++++++++++++++++++-- > sequencer.h | 2 + > t/t3422-rebase-incompatible-options.sh | 2 - > t/t3433-rebase-options-compatibility.sh | 131 ++++++++++++++++++++++ > 7 files changed, 327 insertions(+), 28 deletions(-) > create mode 100755 t/t3433-rebase-options-compatibility.sh > > diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt > index 0c4f038dd6..1d0e2d27cc 100644 > --- a/Documentation/git-rebase.txt > +++ b/Documentation/git-rebase.txt > @@ -393,16 +393,31 @@ your branch contains commits which were dropped, this option can be used > with `--keep-base` in order to drop those commits from your branch. > > --ignore-whitespace:: > + Behaves differently depending on which backend is selected. > ++ > +'am' backend: When applying a patch, ignore changes in whitespace in > +context lines if necessary. > ++ > +'interactive' backend: Treat lines with only whitespace changes as > +unchanged for the sake of a three-way merge. > + > --whitespace=