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

Incorrect diff-parseopt conversion?

From
Ramsay Jones <ramsay@ramsayjones.plus.com>
Date
May 21, 2019, 19:56 UTC
Message-ID
<82f79cd9-5273-b9a4-744d-f5fa95dd1f47@ramsayjones.plus.com>
Hi Duy,

I am in the middle of rebasing a long running branch onto current master (v2.22.0-rc1) and noticed something odd with commit af2f368091 ("diff-parseopt: convert --output-*", 2019-02-21).

As part of the branch I am rebasing, I have defined a new OPT_LL_CALLBACK() macro[1], which I had intended to apply to the 'output' option to diff. However, commit af2f368091 defines that option thus:

+               { OPTION_CALLBACK, 0, "output", options, N_("<file>"),
+                 N_("Output to a specific file"),
+                 PARSE_OPT_NONEG, NULL, 0, diff_opt_output },

Note that the 'option type' is given as OPTION_CALLBACK, not as OPTION_LOWLEVEL_CALLBACK. Is this intended?

ATB, Ramsay Jones

[1] Yes, the reason my branch is long running is because we keep changing the same files! We have both defined new OPT_() macros, some with the same name ... ;-)

Next: Duy Nguyen
Message 1 of 6 in “Incorrect diff-parseopt conversion?”
  1. Ramsay JonesMay 21, 2019
  2. Duy NguyenMay 22, 2019
  3. Ramsay JonesMay 22, 2019
  4. Duy NguyenMay 24, 2019
  5. Ævar Arnfjörð BjarmasonMay 24, 2019
  6. Duy NguyenMay 25, 2019

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.