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

Re: [PATCH] git-rm: Fix to properly handle files with spaces, tabs, newlines, etc.

From
Junio C Hamano <junkio@cox.net>
Date
Feb 23, 2006, 01:07 UTC
Message-ID
<7vbqwylw64.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<873biasyew.wl%cworth@cworth.org>
Carl Worth <cworth@cworth.org> writes:
>  Please ignore the previous patch. This is what I intended to send.
Ahh.  I was wondering...
Show 5 quoted lines
>  (For as useful as the index is---and yes, I have found it very
>  useful---I still find it easy to inadvertently commit stale data with
>  it. I guess what might help me is a command to update into the index
>  all files that are currently in the "updated but not checked in (will
>  commit)" state as reported by git status. Does such a command exist?)
No.  I do not do this myself, but this one-liner should work:
	git diff --name-only "$@" | git update-index --stdin
[from another message]
Show 5 quoted lines
> PS. What's the syntax/tool support for just replying to an existing
> message, and at the end inserting a patch with its own subject and
> commit message? Here I've manually whacked the subject and put the
> commit message above my reply (in the style of git-format-patch) but
> that seems inelegant.
YMMV depending on the MUA you use, of course.

I start [REPLY], have my MUA quote the original and write response while trimming excess quote, just as usual. When I need to add a patch, then I remove all that with \C-w (kill-region), read a format-patch output into the same mail buffer, and then \C-y (yank) to paste the "usual correspondence" part below the three-dash lines. Yes, it's all manual. I presume it would be easy to write a few-liner Emacs macro to do this though...

Previous: Carl WorthNext: Alex Riesen
Message 12 of 15 in “Add new git-rm command with documentation”
  1. Add new git-rm command with documentationCarl Worth, Feb 21, 2006
  2. Krzysiek PawlikFeb 21, 2006
  3. Shawn PearceFeb 21, 2006
  4. Krzysiek PawlikFeb 21, 2006
  5. Shawn PearceFeb 21, 2006
  6. Krzysiek PawlikFeb 21, 2006
  7. Carl WorthFeb 21, 2006
  8. Carl WorthFeb 21, 2006
  9. Junio C HamanoFeb 22, 2006
  10. git-rm: Fix to properly handle files with spaces, tabs, newlines, etc.Carl Worth, Feb 23, 2006
  11. Carl WorthFeb 23, 2006
  12. Junio C HamanoFeb 23, 2006
  13. Alex RiesenFeb 24, 2006
  14. Junio C HamanoFeb 25, 2006
  15. Johannes SchindelinFeb 21, 2006

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.