| blob | d7b5d4fe8c1e3fbc0c856071ee5d7299b6994e34 |
4 <head>
9 /* Debug borders */
11 /*
12 border: 1px solid red;
13 */
14 }
16 body {
18 }
20 a {
23 }
26 }
28 em {
31 }
33 strong {
36 }
38 tt {
40 }
48 }
52 }
53 h2 {
55 }
56 h3 {
58 }
59 h3 + * {
61 }
66 }
68 hr {
70 }
72 p {
75 }
79 }
81 pre {
84 }
86 span#author {
91 }
92 span#email {
93 }
96 }
98 div#footer {
104 }
105 div#footer-text {
108 }
109 div#footer-badges {
112 }
114 div#preamble {
117 }
123 }
127 }
131 }
133 /* Block element titles. */
141 }
144 }
148 }
151 }
154 }
160 }
166 }
171 }
175 }
180 }
183 }
187 }
188 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
191 }
200 }
204 }
209 }
215 dl {
218 }
219 dt {
224 }
227 }
231 }
234 }
237 }
240 }
243 }
246 }
253 }
257 }
258 thead {
261 }
262 tfoot {
264 }
267 }
270 }
271 /* Because the table frame attribute is overriden by CSS in most browsers. */
274 }
278 }
282 }
288 }
291 }
294 }
300 }
303 }
307 }
311 }
315 }
317 div#toctitle {
324 }
329 }
333 }
337 }
341 }
342 /* Overrides for manpage documents */
343 h1 {
348 }
349 h2 {
351 }
354 }
358 }
360 /* Workarounds for IE6's broken and incomplete CSS2. */
366 }
373 }
379 }
384 }
388 }
392 }
397 }
399 /* IE6 sets dynamically generated links as visited. */
401 </style>
402 </head>
403 <body>
405 <h1>
406 git-rm(1) Manual Page
407 </h1>
410 <p>git-rm -
411 Remove files from the working tree and from the index
412 </p>
413 </div>
414 </div>
418 <div class="verseblock-content"><em>git rm</em> [-f | --force] [-n] [-r] [--cached] [--ignore-unmatch] [--quiet] [--] <file>…</div>
420 </div></div>
421 </div>
426 (There is no option to remove a file only from the working tree
428 The files being removed have to be identical to the tip of the branch,
429 and no updates to their contents can be staged in the index,
432 match either the tip of the branch or the file on disk,
433 allowing the file to be removed from just the index.</p></div>
434 </div>
440 </dt>
441 <dd>
442 <p>
444 remove all matching files. If you want git to expand
445 file glob characters, you may need to shell-escape them.
446 A leading directory name
448 given to remove all files in the directory, and recursively
449 all sub-directories,
451 </p>
452 </dd>
454 -f
455 </dt>
457 --force
458 </dt>
459 <dd>
460 <p>
461 Override the up-to-date check.
462 </p>
463 </dd>
465 -n
466 </dt>
468 --dry-run
469 </dt>
470 <dd>
471 <p>
472 Don’t actually remove any file(s). Instead, just show
473 if they exist in the index and would otherwise be removed
474 by the command.
475 </p>
476 </dd>
478 -r
479 </dt>
480 <dd>
481 <p>
482 Allow recursive removal when a leading directory name is
483 given.
484 </p>
485 </dd>
487 --
488 </dt>
489 <dd>
490 <p>
491 This option can be used to separate command-line options from
492 the list of files, (useful when filenames might be mistaken
493 for command-line options).
494 </p>
495 </dd>
497 --cached
498 </dt>
499 <dd>
500 <p>
501 Use this option to unstage and remove paths only from the index.
502 Working tree files, whether modified or not, will be
503 left alone.
504 </p>
505 </dd>
507 --ignore-unmatch
508 </dt>
509 <dd>
510 <p>
511 Exit with a zero status even if no files matched.
512 </p>
513 </dd>
515 -q
516 </dt>
518 --quiet
519 </dt>
520 <dd>
521 <p>
523 for each file removed. This option suppresses that output.
524 </p>
525 </dd>
526 </dl></div>
527 </div>
531 file glob patterns, or leading directory names. The command
532 removes only the paths that are known to git. Giving the name of
533 a file that you have not told git about does not remove that file.</p></div>
539 </div>
540 <h2 id="_removing_files_that_have_disappeared_from_the_filesystem">REMOVING FILES THAT HAVE DISAPPEARED FROM THE FILESYSTEM</h2>
543 the paths that have disappeared from the filesystem. However,
544 depending on the use case, there are several ways that can be
545 done.</p></div>
546 <h3 id="_using_8220_git_commit_a_8221">Using “git commit -a”</h3><div style="clear:left"></div>
548 of tracked files in the working tree and record all removals of
551 automatically notice and record all removals. You can also have a
553 <h3 id="_using_8220_git_add_a_8221">Using “git add -A”</h3><div style="clear:left"></div>
555 want to record both the removal of paths and additions of new paths
556 as well as modifications of existing paths.</p></div>
558 tree using this command:</p></div>
562 </div></div>
566 modifications in the working tree is:</p></div>
570 </div></div>
574 that are no longer present in the working tree (perhaps because
576 use the following command:</p></div>
580 </div></div>
581 </div>
587 </dt>
588 <dd>
589 <p>
592 </p>
594 example; this lets git, and not the shell, expand the pathnames
596 </dd>
599 </dt>
600 <dd>
601 <p>
602 Because this example lets the shell expand the asterisk
603 (i.e. you are listing the files explicitly), it
605 </p>
606 </dd>
607 </dl></div>
608 </div>
612 </div>
616 </div>
620 </div>
621 </div>
622 </body>
623 </html>