summaryrefslogtreecommitdiffstats
path: root/git-rm.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junio@kernel.org>2010-12-08 02:06:14 +0000
committerJunio C Hamano <junio@kernel.org>2010-12-08 02:06:14 +0000
commit28e6d1f42c813caecf9c05f855e0d17184e01b62 (patch)
tree10af6044cb2cf9ec4af8afdc8d6c146daf822c64 /git-rm.txt
parent2e6ded8990e867c457680899597363f3c1dd07f6 (diff)
downloadgit-htmldocs-28e6d1f42c813caecf9c05f855e0d17184e01b62.tar.gz
Autogenerated HTML docs for v1.7.3.3-402-ga48aa
Diffstat (limited to 'git-rm.txt')
-rw-r--r--git-rm.txt12
1 files changed, 6 insertions, 6 deletions
diff --git a/git-rm.txt b/git-rm.txt
index 71e3d9fc2..0adbe8b1f 100644
--- a/git-rm.txt
+++ b/git-rm.txt
@@ -89,8 +89,8 @@ the paths that have disappeared from the filesystem. However,
depending on the use case, there are several ways that can be
done.
-Using "git commit -a"
-~~~~~~~~~~~~~~~~~~~~~
+Using ``git commit -a''
+~~~~~~~~~~~~~~~~~~~~~~~
If you intend that your next commit should record all modifications
of tracked files in the working tree and record all removals of
files that have been removed from the working tree with `rm`
@@ -98,8 +98,8 @@ files that have been removed from the working tree with `rm`
automatically notice and record all removals. You can also have a
similar effect without committing by using `git add -u`.
-Using "git add -A"
-~~~~~~~~~~~~~~~~~~
+Using ``git add -A''
+~~~~~~~~~~~~~~~~~~~~
When accepting a new code drop for a vendor branch, you probably
want to record both the removal of paths and additions of new paths
as well as modifications of existing paths.
@@ -111,8 +111,8 @@ tree using this command:
git ls-files -z | xargs -0 rm -f
----------------
-and then "untar" the new code in the working tree. Alternately
-you could "rsync" the changes into the working tree.
+and then untar the new code in the working tree. Alternately
+you could 'rsync' the changes into the working tree.
After that, the easiest way to record all removals, additions, and
modifications in the working tree is: