[PATCH 0/2] use "working trees" instead of "worktree" in our API

From: Stefan Beller <sbeller@google.com>
Date: Mar 20, 2017, 19:22 UTC
Message-ID: <20170320192225.18928-1-sbeller@google.com>
In-Reply-To: <20170320185038.GU26789@aiede.mtv.corp.google.com>

> For what it's worth, this conversation makes me think it was a mistake
> to call this construct a worktree.

So the way forward is to purge the use of "worktree" meaning actual working trees?

Thanks, Stefan

Stefan Beller (2):
  git.c: introduce --working-tree superseding --work-tree
  revparse: introduce --is-inside-working-tree

 Documentation/git-rev-parse.txt |  4 ++--
 Documentation/git.txt           | 12 ++++++------
 builtin/rev-parse.c             |  3 ++-
 git.c                           |  5 +++--
 4 files changed, 13 insertions(+), 11 deletions(-)

-- 
2.12.0.306.g4a9b9b32d4.dirty

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