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

Re: suggestion: git status = restored

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Mar 29, 2011, 18:56 UTC
Message-ID
<vpqr59piwn2.fsf@bauges.imag.fr>
In-Reply-To
<4D92179D.6050102@gmail.com>
Neal Kreitzinger <nkreitzinger@gmail.com> writes:
> I see your point about the current worktree/index/HEAD.  I'm not a git
> developer, but my idea is based on the concept that the sha-1 of the
> content already exists in the object store regardless of its path(s).

That wouldn't work: the blob is added to the object store at the time of "git add", so at the time of "git status", it has to exist in the object store, whether it's "restored" or "totally new".

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Junio C HamanoNext: Jeff King
Message 5 of 6 in “suggestion: git status = restored”
  1. Neal KreitzingerMar 25, 2011
  2. Jeff KingMar 29, 2011
  3. Neal KreitzingerMar 29, 2011
  4. Junio C HamanoMar 29, 2011
  5. Matthieu MoyMar 29, 2011
  6. Jeff KingMar 29, 2011

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.