From: Phillip Wood Date: Tue, 07 Jan 2020 14:43:33 GMT Subject: Re: [PATCH v3 10/15] rebase: add an --am option Message-ID: <8f2fa083-114a-011f-1480-ae0ebd67d814@gmail.com> In-Reply-To: <1df11f0b5105b1f602fdd723e0f74565e436faba.1577217299.git.gitgitgadget@gmail.com> Hi Elijah On 24/12/2019 19:54, Elijah Newren via GitGitGadget wrote: > From: Elijah Newren > > Currently, this option doesn't do anything except error out if any > options requiring the interactive-backend are also passed. However, > when we make the default backend configurable later in this series, this > flag will provide a way to override the config setting. I wonder if we really want to add a new option that we know we don't want to keep in the long term. Could we not just default to the interactive backend and fallback to the am backend if the user passes any of the am-based options on the commandline? i.e. reverse the current situation of defaulting to the am backend and selecting the interactive backend when the user passes certain options. Best Wishes Phillip > Signed-off-by: Elijah Newren > --- > Documentation/git-rebase.txt | 11 ++++++++++- > builtin/rebase.c | 18 +++++++++++++++++- > 2 files changed, 27 insertions(+), 2 deletions(-) > > diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt > index f1ace07c38..cf1ac2e359 100644 > --- a/Documentation/git-rebase.txt > +++ b/Documentation/git-rebase.txt > @@ -258,6 +258,13 @@ See also INCOMPATIBLE OPTIONS below. > original branch. The index and working tree are also left > unchanged as a result. > > +--am: > + Use git-am internally to rebase. This option may become a > + no-op in the future once the interactive backend handles > + everything the am one does. > ++ > +See also INCOMPATIBLE OPTIONS below. > + > --empty={drop,keep,ask}:: > How to handle commits that become empty (because they contain a > subset of already upstream changes) or start empty. With drop > @@ -372,7 +379,7 @@ See also INCOMPATIBLE OPTIONS below. > Ensure at least lines of surrounding context match before > and after each change. When fewer lines of surrounding > context exist they all must match. By default no context is > - ever ignored. > + ever ignored. Implies --am. > + > See also INCOMPATIBLE OPTIONS below. > > @@ -417,6 +424,7 @@ with `--keep-base` in order to drop those commits from your branch. > --whitespace=