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

Re: What's cooking in git.git (Feb 2013, #01; Fri, 1)

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 3, 2013, 05:44 UTC
Message-ID
<7vlib69cjh.fsf@alter.siamese.dyndns.org>
In-Reply-To
<7vwqur8z4s.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
Regarding these two topics....
Show 32 quoted lines
> * da/mergetool-docs (2013-01-30) 7 commits
>  - doc: generate a list of valid merge tools
>  - mergetool--lib: list user configured tools in '--tool-help'
>  - fixup! doc: generate a list of valid merge tools
>  - fixup! mergetool--lib: add functions for finding available tools
>  - mergetool--lib: add functions for finding available tools
>  - mergetool--lib: improve the help text in guess_merge_tool()
>  - mergetool--lib: simplify command expressions
>  (this branch uses jk/mergetool.)
>
>  Build on top of the clean-up done by jk/mergetool and automatically
>  generate the list of mergetool and difftool backends the build
>  supports to be included in the documentation.
>
>  Will merge to 'next', after squashing the fixup! commits from John
>  Keeping.
>
>
> * jk/mergetool (2013-01-28) 8 commits
>  - mergetools: simplify how we handle "vim" and "defaults"
>  - mergetool--lib: don't call "exit" in setup_tool
>  - mergetool--lib: improve show_tool_help() output
>  - mergetools/vim: remove redundant diff command
>  - git-difftool: use git-mergetool--lib for "--tool-help"
>  - git-mergetool: don't hardcode 'mergetool' in show_tool_help
>  - git-mergetool: remove redundant assignment
>  - git-mergetool: move show_tool_help to mergetool--lib
>  (this branch is used by da/mergetool-docs.)
>
>  Cleans up mergetool/difftool combo.
>
>  This is looking ready for 'next'.

Do the tips of these two topics look reasonable to both of you, or are there anything you sent but I missed?

Previous: Junio C HamanoNext: David Aguilar
Message 2 of 5 in “What's cooking in git.git (Feb 2013, #01; Fri, 1)”
  1. Junio C HamanoFeb 1, 2013
  2. Junio C HamanoFeb 3, 2013
  3. David AguilarFeb 3, 2013
  4. John KeepingFeb 3, 2013
  5. Junio C HamanoFeb 3, 2013

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.