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

git-name-rev --undefined / --always

From
LWLea Wiemann <lewiemann@gmail.com>
Date
Jun 5, 2008, 23:49 UTC
Message-ID
<48487B7F.5000909@gmail.com>

The name-rev command has an option --undefined (which is not documented in git-name-rev.txt) that doesn't do anything. If you look at builtin-name-rev.c, allow_undefined never gets set to anything but 1, I think. In that case --undefined could be made a dummy option for compatibility and the allow_undefined code could be ripped out.

In the same file, there's also an "else if (always)" clause that, if allow_undefined is indeed always true, never gets run. "git-name-ref --tags --always master" still prints "undefined" despite the --always option. (--always is undocumented as well.)

Perhaps someone more knowledgeable should take a look at this (and maybe write up a test case or two), I don't feel confident submitting patches to this file.

-- Lea
Message 1 of 1 in “git-name-rev --undefined / --always”
  1. Lea WiemannJun 5, 2008

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.