| blob | 759a0ff1e7961259e77e1fabc3cff3788c31a623 |
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 git-notes(1) Manual Page
574 </h1>
577 <p>git-notes -
578 Add or inspect object notes
579 </p>
580 </div>
581 </div>
587 <em>git notes</em> add [-f] [-F <file> | -m <msg> | (-c | -C) <object>] [<object>]
589 <em>git notes</em> append [-F <file> | -m <msg> | (-c | -C) <object>] [<object>]
599 </div></div>
600 </div>
604 the objects themselves.</p></div>
605 <div class="paragraph"><p>By default, notes are saved to and read from <tt>refs/notes/commits</tt>, but
606 this default can be overridden. See the OPTIONS, CONFIGURATION, and
607 ENVIRONMENT sections below. If this ref does not exist, it will be
608 quietly created when it is first needed to store a note.</p></div>
611 the original commit message. To distinguish these notes from the
612 message stored in the commit object, the notes are indented like the
613 message, after an unindented line saying "Notes (<refname>):" (or
617 <div class="paragraph"><p>See the "notes.rewrite.<command>" configuration for a way to carry
618 notes across commands that rewrite commits.</p></div>
619 </div>
624 list
625 </dt>
626 <dd>
627 <p>
628 List the notes object for a given object. If no object is
629 given, show a list of all note objects and the objects they
630 annotate (in the format "<note object> <annotated object>").
631 This is the default subcommand if no subcommand is given.
632 </p>
633 </dd>
635 add
636 </dt>
637 <dd>
638 <p>
639 Add notes for a given object (defaults to HEAD). Abort if the
642 to supply the notes contents), then - instead of aborting -
644 subcommand).
645 </p>
646 </dd>
648 copy
649 </dt>
650 <dd>
651 <p>
652 Copy the notes for the first object onto the second object.
653 Abort if the second object already has notes, or if the first
654 object has none (use -f to overwrite existing notes to the
655 second object). This subcommand is equivalent to:
657 </p>
662 </div></div>
663 <div class="paragraph"><p>on standard input, and copy the notes from each <from-object> to its
666 </dd>
668 append
669 </dt>
670 <dd>
671 <p>
672 Append to the notes of an existing object (defaults to HEAD).
673 Creates a new notes object if needed.
674 </p>
675 </dd>
677 edit
678 </dt>
679 <dd>
680 <p>
681 Edit the notes for a given object (defaults to HEAD).
682 </p>
683 </dd>
685 show
686 </dt>
687 <dd>
688 <p>
689 Show the notes for a given object (defaults to HEAD).
690 </p>
691 </dd>
693 merge
694 </dt>
695 <dd>
696 <p>
697 Merge the given notes ref into the current notes ref.
698 This will try to merge the changes made by the given
699 notes ref (called "remote") since the merge-base (if
700 any) into the current notes ref (called "local").
701 </p>
703 conflicting notes (see the -s/--strategy option) is not given,
704 the "manual" resolver is used. This resolver checks out the
706 and instructs the user to manually resolve the conflicts there.
707 When done, the user can either finalize the merge with
710 </dd>
712 remove
713 </dt>
714 <dd>
715 <p>
716 Remove the notes for given objects (defaults to HEAD). When
717 giving zero or one object from the command line, this is
718 equivalent to specifying an empty note message to
720 </p>
721 </dd>
723 prune
724 </dt>
725 <dd>
726 <p>
727 Remove all notes for non-existing/unreachable objects.
728 </p>
729 </dd>
731 get-ref
732 </dt>
733 <dd>
734 <p>
735 Print the current notes ref. This provides an easy way to
736 retrieve the current notes ref (e.g. from scripts).
737 </p>
738 </dd>
739 </dl></div>
740 </div>
745 -f
746 </dt>
748 --force
749 </dt>
750 <dd>
751 <p>
752 When adding notes to an object that already has notes,
753 overwrite the existing notes (instead of aborting).
754 </p>
755 </dd>
758 </dt>
761 </dt>
762 <dd>
763 <p>
764 Use the given note message (instead of prompting).
766 are concatenated as separate paragraphs.
768 single line between paragraphs will be stripped out.
769 </p>
770 </dd>
773 </dt>
776 </dt>
777 <dd>
778 <p>
780 read the note message from the standard input.
782 single line between paragraphs will be stripped out.
783 </p>
784 </dd>
787 </dt>
790 </dt>
791 <dd>
792 <p>
793 Take the given blob object (for example, another note) as the
795 copy notes between objects.)
796 </p>
797 </dd>
800 </dt>
803 </dt>
804 <dd>
805 <p>
807 the user can further edit the note message.
808 </p>
809 </dd>
812 </dt>
813 <dd>
814 <p>
818 </p>
819 </dd>
821 --ignore-missing
822 </dt>
823 <dd>
824 <p>
825 Do not consider it an error to request removing notes from an
826 object that does not have notes attached to it.
827 </p>
828 </dd>
830 --stdin
831 </dt>
832 <dd>
833 <p>
834 Also read the object names to remove notes from from the standard
835 input (there is no reason you cannot combine this with object
836 names from the command line).
837 </p>
838 </dd>
840 -n
841 </dt>
843 --dry-run
844 </dt>
845 <dd>
846 <p>
847 Do not remove anything; just report the object names whose notes
848 would be removed.
849 </p>
850 </dd>
853 </dt>
856 </dt>
857 <dd>
858 <p>
859 When merging notes, resolve notes conflicts using the given
860 strategy. The following strategies are recognized: "manual"
862 See the "NOTES MERGE STRATEGIES" section below for more
863 information on each notes merge strategy.
864 </p>
865 </dd>
867 --commit
868 </dt>
869 <dd>
870 <p>
873 stored in .git/NOTES_MERGE_WORKTREE. This amends the partial
875 .git/NOTES_MERGE_PARTIAL) by adding the notes in
876 .git/NOTES_MERGE_WORKTREE. The notes ref stored in the
877 .git/NOTES_MERGE_REF symref is updated to the resulting commit.
878 </p>
879 </dd>
881 --abort
882 </dt>
883 <dd>
884 <p>
886 with conflicts. This simply removes all files related to the
887 notes merge.
888 </p>
889 </dd>
891 -q
892 </dt>
894 --quiet
895 </dt>
896 <dd>
897 <p>
898 When merging notes, operate quietly.
899 </p>
900 </dd>
902 -v
903 </dt>
905 --verbose
906 </dt>
907 <dd>
908 <p>
909 When merging notes, be more verbose.
910 When pruning notes, report all object names whose notes are
911 removed.
912 </p>
913 </dd>
914 </dl></div>
915 </div>
919 (usually information to supplement a commit’s message). These blobs
920 are taken from notes refs. A notes ref is usually a branch which
921 contains "files" whose paths are the object names for the objects
922 they describe, with some directory separators included for performance
924 <em>ab</em><tt>/</tt><em>cd</em><tt>/</tt><em>ef</em><tt>/</tt><em>…</em><tt>/</tt><em>abcdef…</em>: a sequence of directory
925 names of two hexadecimal digits each followed by a filename with the
928 You can therefore inspect the history of the notes by invoking, e.g.,
930 which operation triggered the update, and the commit authorship is
932 These details may change in the future.</p></div>
934 object, in which case the history of the notes can be read with
936 </div>
940 conflicting notes in a special work tree for resolving notes conflicts
942 conflicts in that work tree.
943 When done, the user can either finalize the merge with
947 version (i.e. the current notes ref).</p></div>
948 <div class="paragraph"><p>"theirs" automatically resolves notes conflicts in favor of the remote
949 version (i.e. the given notes ref being merged into the current notes
950 ref).</p></div>
952 local and remote versions.</p></div>
953 <div class="paragraph"><p>"cat_sort_uniq" is similar to "union", but in addition to concatenating
954 the local and remote versions, this strategy also sorts the resulting
955 lines, and removes duplicate lines from the result. This is equivalent
956 to applying the "cat | sort | uniq" shell pipeline to the local and
957 remote versions. This strategy is useful if the notes follow a line-based
958 format where one wants to avoid duplicated lines in the merge result.
959 Note that if either the local or remote version contain duplicate lines
960 prior to the merge, these will also be removed by this notes merge
961 strategy.</p></div>
962 </div>
966 available at the time a commit was written.</p></div>
970 $ git show -s 72a144e
971 [...]
974 Notes:
976 </div></div>
978 (non-)format is accepted. You can binary-safely create notes from
982 <pre><tt>$ cc *.c
983 $ blob=$(git hash-object -w a.out)
985 </div></div>
986 <div class="paragraph"><p>(You cannot simply use <tt>git notes --ref=built add -F a.out HEAD</tt>
987 because that is not binary-safe.)
988 Of course, it doesn’t make much sense to display non-text-format notes
990 some special-purpose tools to do something useful with them.</p></div>
991 </div>
996 core.notesRef
997 </dt>
998 <dd>
999 <p>
1000 Notes ref to read and manipulate instead of
1002 This setting can be overridden through the environment and
1003 command line.
1004 </p>
1005 </dd>
1007 notes.displayRef
1008 </dt>
1009 <dd>
1010 <p>
1011 Which ref (or refs, if a glob or specified more than once), in
1015 This setting can be overridden on the command line or by the
1018 </p>
1019 </dd>
1022 </dt>
1023 <dd>
1024 <p>
1027 notes from the original to the rewritten commit. Defaults to
1029 </p>
1031 environment variable.</p></div>
1032 </dd>
1034 notes.rewriteMode
1035 </dt>
1036 <dd>
1037 <p>
1038 When copying notes during a rewrite, what to do if the target
1041 </p>
1042 <div class="paragraph"><p>This setting can be overridden with the <tt>GIT_NOTES_REWRITE_MODE</tt>
1043 environment variable.</p></div>
1044 </dd>
1046 notes.rewriteRef
1047 </dt>
1048 <dd>
1049 <p>
1050 When copying notes during a rewrite, specifies the (fully
1051 qualified) ref whose notes should be copied. May be a glob,
1052 in which case notes in all matching refs will be copied. You
1053 may also specify this configuration several times.
1054 </p>
1056 enable note rewriting.</p></div>
1057 <div class="paragraph"><p>Can be overridden with the <em>GIT_NOTES_REWRITE_REF</em> environment variable.</p></div>
1058 </dd>
1059 </dl></div>
1060 </div>
1066 </dt>
1067 <dd>
1068 <p>
1071 </p>
1072 </dd>
1075 </dt>
1076 <dd>
1077 <p>
1078 Colon-delimited list of refs or globs indicating which refs,
1081 messages.
1083 </p>
1085 does not match any refs is silently ignored.</p></div>
1086 </dd>
1089 </dt>
1090 <dd>
1091 <p>
1092 When copying notes during a rewrite, what to do if the target
1093 commit already has a note.
1096 </p>
1097 </dd>
1100 </dt>
1101 <dd>
1102 <p>
1103 When rewriting commits, which notes to copy from the original
1104 to the rewritten commit. Must be a colon-delimited list of
1105 refs or globs.
1106 </p>
1108 on the <tt>notes.rewrite.<command></tt> and <tt>notes.rewriteRef</tt> settings.</p></div>
1109 </dd>
1110 </dl></div>
1111 </div>
1114 <div class="paragraph"><p>Written by Johannes Schindelin <<a href="mailto:johannes.schindelin@gmx.de">johannes.schindelin@gmx.de</a>> and
1116 </div>
1120 </div>
1124 </div>
1125 </div>
1130 </div>
1131 </div>
1132 </body>
1133 </html>