Re: [PATCH] mergetool--lib: add diffmerge as a pre-configured mergetool option
On Wed, Dec 9, 2009 at 4:08 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 9 quoted lines
> Perhaps it is a better approach to first eject bulk of code for the
> backends we currently support under these case statements into separate
> files, one per backend, move them to mergetool/ subdirectory in the source
> tree, install them as "$(share)/git-core/mergetool/$toolname", and at
> runtime source them? That way, a patch to add a new backend can be as
> simple as adding a new file in mergetool/ and doing nothing else. Also an
> end user can privately add support to a new backend much more easily.
>
> Anybody want to try that approach?
Sure. There may also be value in emulating the mercurial approach:
http://mercurial.selenic.com/wiki/MergeToolConfiguration
I'll give both a shot.
j.
Jay Soffian <jaysoffian@gmail.com>