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

Re: [PATCH] Add new git-rm command with documentation

From
Junio C Hamano <junkio@cox.net>
Date
Feb 22, 2006, 08:19 UTC
Message-ID
<7vaccjst3x.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<87r75ws48c.wl%cworth@cworth.org>
Carl Worth <cworth@cworth.org> writes:
Show 10 quoted lines
> +files=$(
> +    if test -f "$GIT_DIR/info/exclude" ; then
> +	git-ls-files \
> +	    --exclude-from="$GIT_DIR/info/exclude" \
> +	    --exclude-per-directory=.gitignore -- "$@"
> +    else
> +	git-ls-files \
> +	--exclude-per-directory=.gitignore -- "$@"
> +    fi | sort | uniq
> +)

Note you are not using -z, which means we will c-quote the funny characters in the output...

> +case "$show_only" in
> +true)
> +	echo $files
> +	;;

And here $files lack surrounding double quote. For human consumption it might be OK, but I somehow care about a bit of details like this.

> +*)
> +	[[ "$remove_files" = "true" ]] && rm -- $files

Same here. What happens to filenames with IFS letters in them? "git-add" does not use -z and xargs -0 without a good reason.

> +	git-update-index $index_remove_option $verbose $files
> +	;;
> +esac

Even if rm -- $files were quoted correctly, and tried to remove the right files, if some of the files failed to disappear for whatever reason, what happens?

Previous: Carl WorthNext: Carl Worth
Message 9 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.