Re: [PATCHv4] rev-parse: add --show-superproject-working-tree

From: Jonathan Nieder <jrnieder@gmail.com>
Date: Mar 17, 2017, 22:28 UTC
Message-ID: <20170317222842.GP26789@aiede.mtv.corp.google.com>
In-Reply-To: <20170308230742.5185-1-sbeller@google.com>

Hi,

Stefan Beller wrote:

> Add the flag --show-superproject-working-tree to git-rev-parse
> to make it easy to find out if there is a superproject. When no
> superproject exists, the output will be empty.

I'm a little late for this, but think it's better to comment late than never.

After this patch, git rev-parse has two options relating to the working tree:

	git rev-parse --is-inside-work-tree
	git rev-parse --show-superproject-working-tree

Is this inconsistency necessary? Now that there is a "git worktree" command that allows making a second working tree for the same repository, I would have thought we had standardized on work tree as the name in UI.

Thoughts? Jonathan

$ 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.