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

[BUG] 'git ls-files --no-exclude' segfault & co

From
SZEDER Gábor <szeder.dev@gmail.com>
Date
Aug 6, 2018, 16:07 UTC
Message-ID
<CAM0VKj=DDOPDxo_xDvhk2-HUPHfkUcLQTimqmY31yjq5eZiM2Q@mail.gmail.com>

'git ls-files' has the options '--exclude', '--exclude-from', '--exclude-per-directory', and '--exclude-standard', which all work fine. However, it also allows the negated version of all these four options, and they definitely don't work very well:

  $ git ls-files --no-exclude
  Segmentation fault
  $ git ls-files --no-exclude-from
  warning: unable to access '(null)': Bad address
  fatal: cannot use (null) as an exclude file

And '--no-exclude-standard' has the same effect as '--exclude-standard', because its parseopt callback function option_parse_exclude_standard() doesn't bother to look at its 'unset' parameter.

Next: Jeff King
Message 1 of 2 in “[BUG] 'git ls-files --no-exclude' segfault & co”
  1. SZEDER GáborAug 6, 2018
  2. Jeff KingAug 6, 2018

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.