[PATCH] mergetool: Make ECMerge use the settings as specified by the user in the GUI

[PATCH] mergetool: Make ECMerge use the settings as specified by the user in the GUI

[Sebastian Schuberth]

When run from the command line, ECMerge does not automatically use the same
settings for a merge / diff that it would use when starting the GUI and loading
files manually. In the first case the built-in factory defaults would be used,
while in the second case the settings the user has specified in the GUI would
be used, which can be misleading. Specifying the "--default" command line
option changes this behavior so that always the user specfified GUI settings
are used.

Signed-off-by: Sebastian Schuberth <sschuberth@visageimaging.com>
---
 git-mergetool.sh |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/git-mergetool.sh b/git-mergetool.sh
index 5c86f69..fcdec4a 100755
--- a/git-mergetool.sh
+++ b/git-mergetool.sh
@@ -237,9 +237,9 @@ merge_file () {
 	ecmerge)
 	    touch "$BACKUP"
 	    if base_present; then
-		"$merge_tool_path" "$BASE" "$LOCAL" "$REMOTE" --mode=merge3 --to="$MERGED"
+		"$merge_tool_path" "$BASE" "$LOCAL" "$REMOTE" --default --mode=merge3 --to="$MERGED"
 	    else
-		"$merge_tool_path" "$LOCAL" "$REMOTE" --mode=merge2 --to="$MERGED"
+		"$merge_tool_path" "$LOCAL" "$REMOTE" --default --mode=merge2 --to="$MERGED"
 	    fi
 	    check_unchanged
 	    ;;
-- 
1.5.5.GIT

Re: [PATCH] mergetool: Make ECMerge use the settings as specified by the user in the GUI

[Sebastian Schuberth]

> be used, which can be misleading. Specifying the "--default" command line
> option changes this behavior so that always the user specfified GUI settings
> are used.
> 
> Signed-off-by: Sebastian Schuberth <sschuberth@visageimaging.com>

Sorry, I just saw the typo, of course this should say "[...] user specified GUI settings [...]". And the subject has two spaces between "[...] by  the [...]", which should be only one.

-- 
Sebastian Schuberth

Re: [PATCH] mergetool: Make ECMerge use the settings as specified by the user in the GUI

[Steffen Prohaska]

On May 6, 2008, at 12:53 PM, Sebastian Schuberth wrote:

> When run from the command line, ECMerge does not automatically use  
> the same
> settings for a merge / diff that it would use when starting the GUI  
> and loading
> files manually. In the first case the built-in factory defaults  
> would be used,
> while in the second case the settings the user has specified in the  
> GUI would
> be used, which can be misleading. Specifying the "--default" command  
> line
> option changes this behavior so that always the user specfified GUI  
> settings
> are used.


I tested the change and propose to take the patch.  I needed,
however, to remove dos line endings from the patch before it
applied cleanly.

	Steffen

Re: [PATCH] mergetool: Make ECMerge use the settings as specified by the user in the GUI

[Junio C Hamano]

Steffen Prohaska <prohaska@zib.de> writes:

> On May 6, 2008, at 12:53 PM, Sebastian Schuberth wrote:
>
>> When run from the command line, ECMerge does not automatically use
>> the same
>> settings for a merge / diff that it would use when starting the GUI
>> and loading
>> files manually. In the first case the built-in factory defaults
>> would be used,
>> while in the second case the settings the user has specified in the
>> GUI would
>> be used, which can be misleading. Specifying the "--default" command
>> line
>> option changes this behavior so that always the user specfified GUI
>> settings
>> are used.
>
> I tested the change and propose to take the patch.  I needed,
> however, to remove dos line endings from the patch before it
> applied cleanly.

Thanks, I did not have that "apply" problem.  

Queued.

Re: [PATCH] mergetool: Make ECMerge use the settings as specified by the user in the GUI

[Steffen Prohaska]

On May 11, 2008, at 7:31 PM, Junio C Hamano wrote:

>> I tested the change and propose to take the patch.  I needed,
>> however, to remove dos line endings from the patch before it
>> applied cleanly.
>
> Thanks, I did not have that "apply" problem.

Indeed, it is Mac OS X's Mail.app that exports mails with the
wrong line endings.  I did not recognize this before, so I guess
something changed with OS X 10.5, which I installed recently.

	Steffen