Re: [PATCH 10/10] mergetool: use run_mergetool from git-mergetool-lib
- From
Markus Heidelberg <markus.heidelberg@web.de>
- Date
- Apr 2, 2009, 20:13 UTC
- Message-ID
- <200904022213.15173.markus.heidelberg@web.de>
- In-Reply-To
- <20090402200235.GB13817@hashpling.org>
Charles Bailey, 02.04.2009:
Show 20 quoted lines
> On Thu, Apr 02, 2009 at 12:54:22AM +0200, Markus Heidelberg wrote: > > David Aguilar, 01.04.2009: > > > + present=false > > > + base_present && > > > + present=true > > > + > > > + run_mergetool "$merge_tool" "$present" > > > + status=$? > > > > This last line has to be deleted, because the variable 'status' set in > > run_mergetool would be overwritten then. In this case the merge will > > succeed even if it didn't and the file will be staged. > > I think that it would be better if $status stayed as local as > possible. If run_mergetool returned the value of $status as its exit > code then the function will properly return whether the merge > succeeded or not. > > This way run_mergetool's clients can just use its exit code, without > having to know about a magic $status global variable.
Sure. Next time I have to think about the right solution before spreading workarounds.
And shouldn't also check_unchanged() move from git-mergetool.sh to git-mergetool--lib.sh, since it is only used there? Huh, it seems as if some editors for difftool cannot work correctly currently, because this function is used, but defined in git-mergetool.sh.
Markus