| blob | b7ffc480a2241c11c9f5a5f13b15e748060715b7 |
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 }
129 }
133 }
135 /* Block element titles. */
143 }
146 }
150 }
153 }
156 }
162 }
168 }
176 }
181 }
185 }
189 }
190 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
193 }
202 }
206 }
211 }
217 dl {
220 }
221 dt {
226 }
229 }
233 }
236 }
239 }
242 }
245 }
248 }
255 }
259 }
263 }
264 tfoot {
266 }
269 }
272 }
273 /* Because the table frame attribute is overriden by CSS in most browsers. */
276 }
280 }
284 }
290 }
293 }
296 }
302 }
305 }
309 }
313 }
317 }
321 }
326 }
330 }
340 }
345 }
347 div#toc {
349 }
351 div#toctitle {
358 }
363 }
367 }
371 }
375 }
376 /* Overrides for manpage documents */
377 h1 {
382 }
383 h2 {
385 }
388 }
392 }
394 /* Workarounds for IE6's broken and incomplete CSS2. */
400 }
407 }
413 }
418 }
422 }
426 }
431 }
433 /* IE6 sets dynamically generated links as visited. */
435 </style>
437 /*<![CDATA[*/
441 /////////////////////////////////////////////////////////////////////
442 // Table Of Contents generator
443 /////////////////////////////////////////////////////////////////////
445 /* Author: Mihai Bazon, September 2002
446 * http://students.infoiasi.ro/~mishoo
447 *
448 * Table Of Content generator
449 * Version: 0.4
450 *
451 * Feel free to use this script under the terms of the GNU General Public
452 * License, as long as you do not remove or alter this notice.
453 */
455 /* modified by Troy D. Hanson, September 2006. License: GPL */
456 /* modified by Stuart Rackham, 2006, 2009. License: GPL */
458 // toclevels = 1..4.
468 }
470 }
476 }
481 // Function that scans the DOM tree for header elements (the DOM2
482 // nodeIterator API would be a better technique but not supported by all
483 // browsers).
490 }
492 }
493 }
494 }
497 }
512 }
515 },
518 /////////////////////////////////////////////////////////////////////
519 // Footnotes generator
520 /////////////////////////////////////////////////////////////////////
522 /* Based on footnote generation code from:
523 * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
524 */
534 n++;
535 // Use [\s\S] in place of . so multi-line matches work.
536 // Because JavaScript has no s (dotall) regex flag.
547 }
548 }
552 // Process footnoterefs.
561 }
562 }
563 }
564 }
566 }
567 /*]]>*/
568 </script>
569 </head>
570 <body>
572 <h1>
573 gitcli(7) Manual Page
574 </h1>
577 <p>gitcli -
578 git command line interface and conventions
579 </p>
580 </div>
581 </div>
586 </div>
589 <div class="paragraph"><p>This manual describes the convention used throughout git CLI.</p></div>
591 "tree-ish", depending on the context and command) and paths as their
592 arguments. Here are the rules:</p></div>
594 <li>
595 <p>
596 Revisions come first and then paths.
598 <tt>v1.0</tt> and <tt>v2.0</tt> are revisions and <tt>arch/x86</tt> and <tt>include/asm-x86</tt>
599 are paths.
600 </p>
601 </li>
602 <li>
603 <p>
604 When an argument can be misunderstood as either a revision or a path,
607 tree. Please show changes between the version I staged in the index
609 between the HEAD commit and the work tree as a whole". You can say
611 </p>
612 </li>
613 <li>
614 <p>
616 out and asking you to disambiguate when ambiguous. E.g. if you have a
619 disambiguate.
620 </p>
621 </li>
622 </ul></div>
623 <div class="paragraph"><p>When writing a script that is expected to handle random user-input, it is
624 a good practice to make it explicit which arguments are which by placing
626 <div class="paragraph"><p>Here are the rules regarding the "flags" that you should follow when you are
627 scripting git:</p></div>
629 <li>
630 <p>
631 it’s preferred to use the non dashed form of git commands, which means that
633 </p>
634 </li>
635 <li>
636 <p>
639 </p>
640 </li>
641 <li>
642 <p>
646 for long options. An option that takes optional option-argument must be
648 </p>
649 </li>
650 <li>
651 <p>
652 when you give a revision parameter to a command, make sure the parameter is
653 not ambiguous with a name of a file in the work tree. E.g. do not write
656 </p>
657 </li>
658 </ul></div>
659 </div>
662 <div class="paragraph"><p>From the git 1.5.4 series and further, many git commands (not all of them at the
663 time of the writing though) come with an enhanced option parser.</p></div>
664 <div class="paragraph"><p>Here is an exhaustive list of the facilities provided by this option parser.</p></div>
666 <div class="paragraph"><p>Commands which have the enhanced option parser activated all understand a
667 couple of magic command line options:</p></div>
670 -h
671 </dt>
672 <dd>
673 <p>
674 gives a pretty printed usage of the command.
675 </p>
678 <pre><tt>$ git describe -h
681 --contains find the tag that comes after the commit
682 --debug debug search strategy on stderr
683 --all use any ref in .git/refs
684 --tags use any tag in .git/refs/tags
687 </div></div>
688 </dd>
690 --help-all
691 </dt>
692 <dd>
693 <p>
694 Some git commands take options that are only used for plumbing or that
695 are deprecated, and such options are hidden from the default usage. This
696 option gives the full list of options.
697 </p>
698 </dd>
699 </dl></div>
701 <div class="paragraph"><p>Options with long option names can be negated by prefixing <tt>--no-</tt>. For
702 example, <tt>git branch</tt> has the option <tt>--track</tt> which is <em>on</em> by default. You
705 <h3 id="_aggregating_short_options">Aggregating short options</h3><div style="clear:left"></div>
706 <div class="paragraph"><p>Commands that support the enhanced option parser allow you to aggregate short
709 <h3 id="_separating_argument_from_the_option">Separating argument from the option</h3><div style="clear:left"></div>
710 <div class="paragraph"><p>You can write the mandatory option parameter to an option as a separate
711 word on the command line. That means that all the following uses work:</p></div>
714 <pre><tt>$ git foo --long-opt=Arg
715 $ git foo --long-opt Arg
716 $ git foo -oArg
717 $ git foo -o Arg</tt></pre>
718 </div></div>
719 <div class="paragraph"><p>However, this is <strong>NOT</strong> allowed for switches with an optional value, where the
723 <pre><tt>$ git describe --abbrev HEAD # correct
724 $ git describe --abbrev=10 HEAD # correct
726 </div></div>
727 </div>
732 options. Sometimes people incorrectly think that, because
733 the index was originally called cache, these two are
735 different things.</p></div>
737 <li>
738 <p>
742 without a commit to specify from which commit to look for
743 strings in, usually works on files in the working tree,
745 the index.
746 </p>
747 </li>
748 <li>
749 <p>
753 merges changes recorded in a stash to the working tree,
755 the index as well.
756 </p>
757 </li>
758 </ul></div>
761 only affects the files in the working tree, but with
764 entries.</p></div>
765 <div class="paragraph"><p>See also <a href="http://marc.info/?l=git&m=116563135620359">http://marc.info/?l=git&m=116563135620359</a> and
766 <a href="http://marc.info/?l=git&m=119150393620273">http://marc.info/?l=git&m=119150393620273</a> for further
767 information.</p></div>
768 </div>
772 </div>
773 </div>
778 </div>
779 </div>
780 </body>
781 </html>