Re: What's cooking in git.git (Feb 2020, #06; Fri, 28)

Elijah Newren [off-list ref] writes:

configuration setting.  I'm not the best at wording these release
notes, but something along the lines of:

"git rebase" has learned to use the merge backend by default, while
allowing "--apply" option to go back to the traditional apply backend,
or allowing an alternate default to be set via the new rebase.backend
configuration variable.  This series also renames the backends from
"interactive" (or "sequencer") to "merge" and from "am" to "apply".

Thanks.  

 "git rebase" has learned to use the merge backend (i.e. the
 machinery that drives "rebase -i") by default, while allowing
 "--apply" option to use the "apply" backend (e.g. the moral
 equivalent of "format-patch piped to am").  The rebase.backend
 configuration variable can be set to customize.