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

Re: [PATCH 2/2] git-rm doc: Describe how to sync index & work tree

From
Björn Gustavsson <bgustavsson@gmail.com>
Date
Dec 8, 2009, 06:19 UTC
Message-ID
<6672d0160912072219g4326bb5pde7bd02c09a9556a@mail.gmail.com>
In-Reply-To
<7vpr6qze4i.fsf@alter.siamese.dyndns.org>
2009/12/7 Junio C Hamano <gitster@pobox.com>:
> I think mentioning "add -u" in the same section as "commit -a" would be
> helpful, as these two are more for user's own development (as opposed to
> vendor-code-drop).  I'd perhaps squash something like this in.  Please say
> "yes", "don't, it is horrible", or something in between ;-)
Yes, but...
> -automatically notice and record all removals.
> +automatically notice and record all removals.  `git add -u`
> +can be used for a similar effect without commiting.
s/commiting/committing/
-- 
Björn Gustavsson, Erlang/OTP, Ericsson AB
Previous: Björn Gustavsson
Message 4 of 4 in “git-rm doc: Describe how to sync index & work tree”
  1. 2/2 git-rm doc: Describe how to sync index & work treeBjörn Gustavsson, Dec 7, 2009
  2. Junio C HamanoDec 7, 2009
  3. Björn GustavssonDec 8, 2009
  4. Björn GustavssonDec 8, 2009

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.