Re: [PATCH v4 20/21] range-diff: make --dual-color the default mode
- From
Thomas Gummerer <t.gummerer@gmail.com>
- Date
- Jul 29, 2018, 21:33 UTC
- Message-ID
- <20180729213325.GC9955@hank.intra.tgummerer.com>
- In-Reply-To
- <b370468e71af2b8c7ffa0e31f3a3910d15897ab4.1532210683.git.gitgitgadget@gmail.com>
On 07/21, Johannes Schindelin via GitGitGadget wrote:
Show 8 quoted lines
> From: Johannes Schindelin <johannes.schindelin@gmx.de> > > After using this command extensively for the last two months, this > developer came to the conclusion that even if the dual color mode still > leaves a lot of room for confusion about what was actually changed, the > non-dual color mode is substantially worse in that regard. > > Therefore, we really want to make the dual color mode the default.
Ah and here we're making it default, so I wouldn't need a `rangeDiff.dualColor` config variable anymore. Even better!
Show 8 quoted lines
> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> > --- > Documentation/git-range-diff.txt | 32 +++++++++++++++----------- > builtin/range-diff.c | 10 ++++---- > contrib/completion/git-completion.bash | 2 +- > 3 files changed, 25 insertions(+), 19 deletions(-) > > [...]