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

Re: [PATCH v7 4/4] vimdiff: add description to already existing diff/merge tools

From
Philippe Blain <levraiphilippeblain@gmail.com>
Date
Mar 29, 2022, 17:24 UTC
Message-ID
<f56a7a0b-8525-c4cc-7bc7-5ac4bba59206@gmail.com>
In-Reply-To
<xmqqh77gww6c.fsf@gitster.g>
Hi Junio, Fernando,
Le 2022-03-29 à 12:38, Junio C Hamano a écrit :
Show 10 quoted lines
> Fernando Ramos <greenfoo@u92.eu> writes:
> 
>> ---
> 
> Missing log message and sign off.  "add description" tells us what
> it did, which is easily visible in the patch text already.  The log
> message should say why we are adding them, and the rationale has to
> be better than "adding is better than not adding".  E.g. "in output
> of X and Y, we only show the names without explanation on what they
> are, which is not helpful enough" would be a helpful log message.

I might add that the prefix of the commit message title should be changed to 'mergetools: '

Show 6 quoted lines
> 
> Doesn't the change in [3/4] to include these strings in generated
> mergetools-*.txt file depend on this in place?
> 
> Thanks.
> 

The list of available values are already generated in the mergetools-diff.txt and mergetools-merge.txt files before this series. After 3/4 we also include the description of the values. In 3/4 descriptions are only added for vimdiff and friends, so the rest of the tools would simply be listed without descriptions. After 4/4 all tools have a description.

Previous: Junio C HamanoNext: Junio C Hamano
Message 6 of 37 in “vimdiff: new implementation with layout support”
  1. 0/4 vimdiff: new implementation with layout supportFernando Ramos, Mar 28, 2022
  2. 1/4 vimdiff: new implementation with layout supportFernando Ramos, Mar 28, 2022
  3. 2/4 vimdiff: integrate layout tests in the unit tests framework ('t' folder)Fernando Ramos, Mar 28, 2022
  4. 4/4 vimdiff: add description to already existing diff/merge toolsFernando Ramos, Mar 28, 2022
  5. Junio C HamanoMar 29, 2022
  6. Philippe BlainMar 29, 2022
  7. Junio C HamanoMar 29, 2022
  8. Fernando RamosMar 29, 2022
  9. 3/4 vimdiff: add tool documentationFernando Ramos, Mar 28, 2022
  10. Fernando RamosMar 28, 2022
  11. Junio C HamanoMar 29, 2022
  12. fixup! vimdiff: add tool documentationPhilippe Blain, Mar 29, 2022
  13. Junio C HamanoMar 29, 2022
  14. Philippe BlainMar 29, 2022
  15. Junio C HamanoMar 29, 2022
  16. Philippe BlainMar 29, 2022
  17. Philippe BlainMar 29, 2022
  18. Philippe BlainMar 29, 2022
  19. Fernando RamosMar 29, 2022
  20. 0/5 vimdiff: new implementation with layout supportFernando Ramos, Mar 29, 2022
  21. 1/5 vimdiff: new implementation with layout supportFernando Ramos, Mar 29, 2022
  22. 2/5 vimdiff: integrate layout tests in the unit tests framework ('t' folder)Fernando Ramos, Mar 29, 2022
  23. 3/5 vimdiff: add tool documentationFernando Ramos, Mar 29, 2022
  24. 4/5 mergetools: add description to all diff/merge toolsFernando Ramos, Mar 29, 2022
  25. 5/5 mergetools: add tools description to `git help config`Fernando Ramos, Mar 29, 2022
  26. Philippe BlainMar 30, 2022
  27. Fernando RamosMar 30, 2022
  28. Philippe BlainMar 30, 2022
  29. 0/4 vimdiff: new implementation with layout supportFernando Ramos, Mar 30, 2022
  30. 1/4 vimdiff: new implementation with layout supportFernando Ramos, Mar 30, 2022
  31. 2/4 vimdiff: integrate layout tests in the unit tests framework ('t' folder)Fernando Ramos, Mar 30, 2022
  32. 3/4 vimdiff: add tool documentationFernando Ramos, Mar 30, 2022
  33. Philippe BlainApr 3, 2022
  34. Junio C HamanoApr 3, 2022
  35. Fernando RamosApr 4, 2022
  36. Junio C HamanoApr 4, 2022
  37. 4/4 mergetools: add description to all diff/merge toolsFernando Ramos, Mar 30, 2022

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.