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

Re: [BUG] git --work-tree=... status

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 12, 2007, 19:32 UTC
Message-ID
<7vlkcgim5w.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20070812185855.GA16704@informatik.uni-freiburg.de>
Uwe Kleine-König  <ukleinek@informatik.uni-freiburg.de> writes:
> The problem seems to be that require_work_tree demands more that I think
> it should.  It calls `git rev-parse --is-inside-work-tree`.

I think the semantics of require_work_tree is (currently and has been) indeed "you are supposed to be inside the work tree".

"git-status $args" is a "git commit --dry-run $args" and $args are often filenames relative to $cwd that name paths to include in the partial commit, so for this particular case I think it is understandable that it wants you to be _IN_ the work tree.

You can propose alternative semantics to "git status" that is defined as "cd_to_toplevel && git diff --cached && git diff" that does not care any of the $args, and I personally am open to such a departure from "commit --dry-run" semantics, which have been there since 1.4.0 days. But that is a huge user level semantics change, and will not belong to the 1.5.X series.

Previous: Uwe Kleine-KönigNext: Uwe Kleine-König
Message 2 of 3 in “[BUG] git --work-tree=... status”
  1. Uwe Kleine-KönigAug 12, 2007
  2. Junio C HamanoAug 12, 2007
  3. Uwe Kleine-KönigAug 17, 2007

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.