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

Re: [PATCH] git-rm: don't remove newly added file without -f

From
Junio C Hamano <junkio@cox.net>
Date
Mar 26, 2007, 21:11 UTC
Message-ID
<7v1wjbwvzl.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20070326185539.GA1650@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 9 quoted lines
> Given this set of commands:
>
>   $ echo "newly added file" >new
>   $ git add new
>   $ git rm new
>
> the file "new" was previously removed from the working
> directory and the index. Because it was not in HEAD, it is
> available only by searching for unreachable objects.

I am not sure if this is a problem, as the user asked it to be removed. It somehow feels to me that the change (I am not convinced your patch should be called a "fix" rather than a "behaviour change") would cause more confusion.

Unstaging request would have looked like "git reset HEAD new", wouldn't it?

Previous: Jeff KingNext: Johannes Schindelin
Message 3 of 7 in “Removing a newly added file”
  1. Santi BéjarMar 26, 2007
  2. git-rm: don't remove newly added file without -fJeff King, Mar 26, 2007
  3. Junio C HamanoMar 26, 2007
  4. Johannes SchindelinMar 26, 2007
  5. Junio C HamanoMar 26, 2007
  6. Jeff KingMar 26, 2007
  7. Junio C HamanoMar 26, 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.