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

Re: Efficient parsing of `status -z` output

From
Jeff King <peff@peff.net>
Date
Mar 9, 2015, 06:49 UTC
Message-ID
<20150309064939.GA30819@peff.net>
In-Reply-To
<20150309061920.GB27128@peff.net>
On Mon, Mar 09, 2015 at 02:19:20AM -0400, Jeff King wrote:
> We don't turn on copy-detection in "git status" by default (only rename
> detection), and I think you are right that there is currently no way to
> turn it on manually.

Actually, I take it back. We do break-detection in git-status, which can lead to finding a copy:

  $ git init
  $ seq 1 1000 >file && git add file && git commit -m base
  $ mv file other
  $ echo foo >file
  $ git add .
  $ git status --short
  M  file
  C  file -> other
-Peff
Previous: Jeff KingNext: Matthew Rothenberg
Message 5 of 7 in “Efficient parsing of `status -z` output”
  1. Matthew RothenbergMar 7, 2015
  2. Junio C HamanoMar 8, 2015
  3. Matthew RothenbergMar 9, 2015
  4. Jeff KingMar 9, 2015
  5. Jeff KingMar 9, 2015
  6. Matthew RothenbergMar 9, 2015
  7. Jeff KingMar 10, 2015

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.