Charles Bailey wrote:
On Fri, Oct 24, 2008 at 11:32:17PM +0100, William Pursell wrote:
If the short option is dropped, the config option should
probably associated with mergetool.<tool>.interactive rather
than mergetool.interactive. (s/interactive/whatever)
I'm not sure I understand your reasoning. The no-prompt/interactive
option affects the behaviour of the mergetool script independent of
which particular merge tool is being used. Why should the presence or
absence of a short option affect whether the config option is global
or per tool?
My thinking is that when using an interactive tool
like vimdiff, the user is probably not going to
care as much about being prompted, or may prefer
to have the prompt in that situation. However,
if they've written a script to do the merge
non-interactively, then the prompt is undesirable.
So a person might want to be prompted with
git mergetool -t vimdiff, and prefer no prompt
with git mergetool -t my-script. Being able
to configure the behavior on a per-tool
basis would allow that.
--
William Pursell
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
