git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 6/8 v2] sh-tools: add a run_merge_tool function

From
David Aguilar <davvid@gmail.com>
Date
Apr 1, 2009, 08:36 UTC
Message-ID
<20090401083649.GA30594@gmail.com>
In-Reply-To
<200904010011.10296.markus.heidelberg@web.de>
On  0, Markus Heidelberg <markus.heidelberg@web.de> wrote:
> James Pickens, 31.03.2009:
> > On Mon, Mar 30, 2009 at 1:11 AM, David Aguilar <davvid@gmail.com> wrote:
> > > This function launches merge tools and will be used to refactor
> > > git-(diff|merge)tool.
sorry this whole series is being rewriten...
Show 26 quoted lines
> > 
> > Thanks for writing difftool; I find it quite useful.  I tried it with
> > tkdiff, and noticed that it shows the 'merge preview' window even though it
> > isn't doing a merge.  If a user with unstaged changes were to carelessly
> > click the 'save and exit' button, his changes could be lost.  So I think
> > it's a good idea to stop the merge preview window from showing up under
> > difftool.  To do that I think you just have to remove the '-o "$MERGED"'
> > option to tkdiff.
> 
> This mail made me see an issue with your patch series. Sorry, I haven't
> seen this earlier, my review was just scratching the surface, I merely
> applied it and looked through it, but didn't actually test it. Lack of
> time.
> 
> The invocations seem to be appropriate only for mergetool, it is just
> the invocations from the old git-mergetool.sh, not from the old
> git-difftool-helper.sh. This means, git-difftool opens 3 files instead
> of 2.
> 
> I think there are preset diff tools, which opened 3 files instead of 2
> before this series (I just tested kdiff3, it opened 3 files). Seems to
> be originated from the fact, that they were initially copied from
> git-mergetool.sh.
> 
> Markus
> 
-- 
		David
Previous: Markus HeidelbergNext: David Aguilar
Message 4 of 5 in “sh-tools: add a run_merge_tool function”
  1. 6/8 sh-tools: add a run_merge_tool functionDavid Aguilar, Mar 30, 2009
  2. James PickensMar 31, 2009
  3. Markus HeidelbergMar 31, 2009
  4. David AguilarApr 1, 2009
  5. David AguilarApr 2, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.