<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/mergetools/defaults, branch master</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=master</id>
<link rel='self' href='https://git.shady.money/git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2013-01-29T03:00:38Z</updated>
<entry>
<title>mergetools: simplify how we handle "vim" and "defaults"</title>
<updated>2013-01-29T03:00:38Z</updated>
<author>
<name>David Aguilar</name>
<email>davvid@gmail.com</email>
</author>
<published>2013-01-27T00:46:12Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=073678b8e6324a155fa99f40eee0637941a70a34'/>
<id>urn:sha1:073678b8e6324a155fa99f40eee0637941a70a34</id>
<content type='text'>
Remove the exceptions for "vim" and "defaults" in the mergetool library
so that every filename in mergetools/ matches 1:1 with the name of a
valid built-in tool.

Define the trivial fallback definition of shell functions in-line in
git-mergetool-lib script, instead of dot-sourcing them from another
file.  The result is much easier to follow.

[jc: squashed in an update from John Keeping as well]

Signed-off-by: David Aguilar &lt;davvid@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>mergetool--lib: Allow custom commands to override built-ins</title>
<updated>2012-09-25T16:04:39Z</updated>
<author>
<name>David Aguilar</name>
<email>davvid@gmail.com</email>
</author>
<published>2012-09-25T07:48:11Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=a427ef7acc9d932d1c203dd2fae67f51c4b1d1e8'/>
<id>urn:sha1:a427ef7acc9d932d1c203dd2fae67f51c4b1d1e8</id>
<content type='text'>
Allow users to override the default commands provided by the
mergetools/* scriptlets.

Users occasionally run into problems where they expect to be
able to override the built-in tool names.  The documentation
does not explicitly mention that built-ins cannot be overridden,
so it's easy to assume that it should work.

Lift this restriction so that built-in tools are handled the
same way as user-configured tools.  Add tests to guarantee this
behavior.

A nice benefit of this change is that it protects users from
having future versions of git trump their custom configuration
with a new built-in tool.

C.f.:

http://stackoverflow.com/questions/7435002/mergetool-from-gitconfig-being-ignored
http://thread.gmane.org/gmane.comp.version-control.msysgit/13188
http://thread.gmane.org/gmane.comp.version-control.git/148267

Signed-off-by: David Aguilar &lt;davvid@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>mergetool--lib: Refactor tools into separate files</title>
<updated>2011-08-19T07:09:19Z</updated>
<author>
<name>David Aguilar</name>
<email>davvid@gmail.com</email>
</author>
<published>2011-08-18T07:23:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=bc7a96a8965d4ce0651689301e1702a942dfb9f0'/>
<id>urn:sha1:bc7a96a8965d4ce0651689301e1702a942dfb9f0</id>
<content type='text'>
Individual merge tools are now defined in a mergetools/$tool
file which is sourced at runtime.

The individual files are installed into $(git --exec-path)/mergetools/.
New tools can be added by creating a new file instead of editing the
git-mergetool--lib.sh scriptlet.

http://thread.gmane.org/gmane.comp.version-control.git/134906/focus=135006

Signed-off-by: David Aguilar &lt;davvid@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
</feed>
