From 2ec4d368f1c1335575c0288b82ac37d2e7058e54 Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Thu, 17 Apr 2008 02:17:53 +0000 Subject: [PATCH] Autogenerated HTML docs for v1.5.5-67-g9a49 --- git-rm.html | 54 ++++++++++++++++++++++++++++++++--------------------- git-rm.txt | 52 +++++++++++++++++++++++++++++++-------------------- 2 files changed, 65 insertions(+), 41 deletions(-) diff --git a/git-rm.html b/git-rm.html index aaff2a603..6e9359e8a 100644 --- a/git-rm.html +++ b/git-rm.html @@ -276,11 +276,16 @@ git-rm(1) Manual Page

DESCRIPTION

-

Remove files from the working tree and from the index. The -files have to be identical to the tip of the branch, and no -updates to its contents must have been placed in the staging -area (aka index). When --cached is given, the staged content has to -match either the tip of the branch or the file on disk.

+

Remove files from the index, or from the working tree and the index. +git rm will not remove a file from just your working directory. +(There is no option to remove a file only from the work tree +and yet keep it in the index; use /bin/rm if you want to do that.) +The files being removed have to be identical to the tip of the branch, +and no updates to their contents can be staged in the index, +though that default behavior can be overridden with the -f option. +When --cached is given, the staged content has to +match either the tip of the branch or the file on disk, +allowing the file to be removed from just the index.

OPTIONS

@@ -291,10 +296,13 @@ match either the tip of the branch or the file on disk.

Files to remove. Fileglobs (e.g. *.c) can be given to - remove all matching files. Also a leading directory name - (e.g. dir to add dir/file1 and dir/file2) can be - given to remove all files in the directory, recursively, - but this requires -r option to be given for safety. + remove all matching files. If you want git to expand + file glob characters, you may need to shell-escape them. + A leading directory name + (e.g. dir to remove dir/file1 and dir/file2) can be + given to remove all files in the directory, and recursively + all sub-directories, + but this requires the -r option to be explicitly given.

@@ -310,8 +318,9 @@ match either the tip of the branch or the file on disk.

- Don't actually remove the file(s), just show if they exist in - the index. + Don't actually remove any file(s). Instead, just show + if they exist in the index and would otherwise be removed + by the command.

@@ -338,9 +347,9 @@ match either the tip of the branch or the file on disk.

- This option can be used to tell the command to remove - the paths only from the index, leaving working tree - files. + Use this option to unstage and remove paths only from the index. + Working tree files, whether modified or not, will be + left alone.

@@ -364,10 +373,14 @@ match either the tip of the branch or the file on disk.

DISCUSSION

-

The list of <file> given to the command can be exact pathnames, -file glob patterns, or leading directory name. The command -removes only the paths that is known to git. Giving the name of +

The <file> list given to the command can be exact pathnames, +file glob patterns, or leading directory names. The command +removes only the paths that are known to git. Giving the name of a file that you have not told git about does not remove that file.

+

File globbing matches across directory boundaries. Thus, given +two directories d and d2, there is a difference between +using git rm 'd*' and git rm 'd/*', as the former will +also remove all of directory d2.

EXAMPLES

@@ -381,15 +394,14 @@ git-rm Documentation/\*.txt Documentation directory and any of its subdirectories.

Note that the asterisk * is quoted from the shell in this -example; this lets the command include the files from -subdirectories of Documentation/ directory.

+example; this lets git, and not the shell, expand the pathnames +of files and subdirectories under the Documentation/ directory.

git-rm -f git-*.sh

- Remove all git-*.sh scripts that are in the index. Because this example lets the shell expand the asterisk (i.e. you are listing the files explicitly), it does not remove subdir/git-foo.sh. @@ -415,7 +427,7 @@ git-rm -f git-*.sh

diff --git a/git-rm.txt b/git-rm.txt index dc36c662a..9c81b72db 100644 --- a/git-rm.txt +++ b/git-rm.txt @@ -11,28 +11,37 @@ SYNOPSIS DESCRIPTION ----------- -Remove files from the working tree and from the index. The -files have to be identical to the tip of the branch, and no -updates to its contents must have been placed in the staging -area (aka index). When --cached is given, the staged content has to -match either the tip of the branch *or* the file on disk. +Remove files from the index, or from the working tree and the index. +`git rm` will not remove a file from just your working directory. +(There is no option to remove a file only from the work tree +and yet keep it in the index; use `/bin/rm` if you want to do that.) +The files being removed have to be identical to the tip of the branch, +and no updates to their contents can be staged in the index, +though that default behavior can be overridden with the `-f` option. +When '--cached' is given, the staged content has to +match either the tip of the branch or the file on disk, +allowing the file to be removed from just the index. OPTIONS ------- ...:: Files to remove. Fileglobs (e.g. `*.c`) can be given to - remove all matching files. Also a leading directory name - (e.g. `dir` to add `dir/file1` and `dir/file2`) can be - given to remove all files in the directory, recursively, - but this requires `-r` option to be given for safety. + remove all matching files. If you want git to expand + file glob characters, you may need to shell-escape them. + A leading directory name + (e.g. `dir` to remove `dir/file1` and `dir/file2`) can be + given to remove all files in the directory, and recursively + all sub-directories, + but this requires the `-r` option to be explicitly given. -f:: Override the up-to-date check. -n, \--dry-run:: - Don't actually remove the file(s), just show if they exist in - the index. + Don't actually remove any file(s). Instead, just show + if they exist in the index and would otherwise be removed + by the command. -r:: Allow recursive removal when a leading directory name is @@ -44,9 +53,9 @@ OPTIONS for command-line options). \--cached:: - This option can be used to tell the command to remove - the paths only from the index, leaving working tree - files. + Use this option to unstage and remove paths only from the index. + Working tree files, whether modified or not, will be + left alone. \--ignore-unmatch:: Exit with a zero status even if no files matched. @@ -59,11 +68,15 @@ OPTIONS DISCUSSION ---------- -The list of given to the command can be exact pathnames, -file glob patterns, or leading directory name. The command -removes only the paths that is known to git. Giving the name of +The list given to the command can be exact pathnames, +file glob patterns, or leading directory names. The command +removes only the paths that are known to git. Giving the name of a file that you have not told git about does not remove that file. +File globbing matches across directory boundaries. Thus, given +two directories `d` and `d2`, there is a difference between +using `git rm \'d\*\'` and `git rm \'d/\*\'`, as the former will +also remove all of directory `d2`. EXAMPLES -------- @@ -72,11 +85,10 @@ git-rm Documentation/\\*.txt:: `Documentation` directory and any of its subdirectories. + Note that the asterisk `\*` is quoted from the shell in this -example; this lets the command include the files from -subdirectories of `Documentation/` directory. +example; this lets git, and not the shell, expand the pathnames +of files and subdirectories under the `Documentation/` directory. git-rm -f git-*.sh:: - Remove all git-*.sh scripts that are in the index. Because this example lets the shell expand the asterisk (i.e. you are listing the files explicitly), it does not remove `subdir/git-foo.sh`. -- 2.26.2