1 <?xml version=
"1.0" encoding=
"UTF-8"?>
2 <!DOCTYPE html PUBLIC
"-//W3C//DTD XHTML 1.1//EN"
3 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
4 <html xmlns=
"http://www.w3.org/1999/xhtml" xml:
lang=
"en">
6 <meta http-equiv=
"Content-Type" content=
"application/xhtml+xml; charset=UTF-8" />
7 <meta name=
"generator" content=
"AsciiDoc 10.2.0" />
8 <title>gitcli(
7)
</title>
9 <style type=
"text/css">
10 /* Shared CSS for AsciiDoc xhtml11 and html5 backends */
14 font-family: Georgia,serif;
18 h1, h2, h3, h4, h5, h6,
19 div.title, caption.title,
20 thead, p.table.header,
22 #author, #revnumber, #revdate, #revremark,
24 font-family: Arial,Helvetica,sans-serif;
28 margin:
1em
5%
1em
5%;
33 text-decoration: underline;
49 h1, h2, h3, h4, h5, h6 {
57 border-bottom:
2px solid silver;
77 border:
1px solid silver;
88 ul
> li { color: #aaa; }
89 ul
> li
> * { color: black; }
91 .monospaced, code, pre {
92 font-family:
"Courier New", Courier, monospace;
99 white-space: pre-wrap;
109 #revnumber, #revdate, #revremark {
114 border-top:
2px solid silver;
120 padding-bottom:
0.5em;
124 padding-bottom:
0.5em;
129 margin-bottom:
1.5em;
131 div.imageblock, div.exampleblock, div.verseblock,
132 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
133 div.admonitionblock {
135 margin-bottom:
1.5em;
137 div.admonitionblock {
139 margin-bottom:
2.0em;
144 div.content { /* Block element content. */
148 /* Block element titles. */
149 div.title, caption.title {
154 margin-bottom:
0.5em;
160 td div.title:first-child {
163 div.content div.title:first-child {
166 div.content + div.title {
170 div.sidebarblock
> div.content {
172 border:
1px solid #dddddd;
173 border-left:
4px solid #f0f0f0;
177 div.listingblock
> div.content {
178 border:
1px solid #dddddd;
179 border-left:
5px solid #f0f0f0;
184 div.quoteblock, div.verseblock {
188 border-left:
5px solid #f0f0f0;
192 div.quoteblock
> div.attribution {
197 div.verseblock
> pre.content {
198 font-family: inherit;
201 div.verseblock
> div.attribution {
205 /* DEPRECATED: Pre version
8.2.7 verse style literal block. */
206 div.verseblock + div.attribution {
210 div.admonitionblock .icon {
214 text-decoration: underline;
216 padding-right:
0.5em;
218 div.admonitionblock td.content {
220 border-left:
3px solid #dddddd;
223 div.exampleblock
> div.content {
224 border-left:
3px solid #dddddd;
228 div.imageblock div.content { padding-left:
0; }
229 span.image img { border-style: none; vertical-align: text-bottom; }
230 a.image:visited { color: white; }
234 margin-bottom:
0.8em;
247 list-style-position: outside;
250 list-style-type: decimal;
253 list-style-type: lower-alpha;
256 list-style-type: upper-alpha;
259 list-style-type: lower-roman;
262 list-style-type: upper-roman;
265 div.compact ul, div.compact ol,
266 div.compact p, div.compact p,
267 div.compact div, div.compact div {
269 margin-bottom:
0.1em;
281 margin-bottom:
0.8em;
284 padding-bottom:
15px;
286 dt.hdlist1.strong, td.hdlist1.strong {
292 padding-right:
0.8em;
298 div.hdlist.compact tr {
307 .footnote, .footnoteref {
311 span.footnote, span.footnoteref {
312 vertical-align: super;
316 margin:
20px
0 20px
0;
320 #footnotes div.footnote {
326 border-top:
1px solid silver;
335 padding-right:
0.5em;
336 padding-bottom:
0.3em;
344 #footer-badges { display: none; }
348 margin-bottom:
2.5em;
356 margin-bottom:
0.1em;
359 div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
376 span.aqua { color: aqua; }
377 span.black { color: black; }
378 span.blue { color: blue; }
379 span.fuchsia { color: fuchsia; }
380 span.gray { color: gray; }
381 span.green { color: green; }
382 span.lime { color: lime; }
383 span.maroon { color: maroon; }
384 span.navy { color: navy; }
385 span.olive { color: olive; }
386 span.purple { color: purple; }
387 span.red { color: red; }
388 span.silver { color: silver; }
389 span.teal { color: teal; }
390 span.white { color: white; }
391 span.yellow { color: yellow; }
393 span.aqua-background { background: aqua; }
394 span.black-background { background: black; }
395 span.blue-background { background: blue; }
396 span.fuchsia-background { background: fuchsia; }
397 span.gray-background { background: gray; }
398 span.green-background { background: green; }
399 span.lime-background { background: lime; }
400 span.maroon-background { background: maroon; }
401 span.navy-background { background: navy; }
402 span.olive-background { background: olive; }
403 span.purple-background { background: purple; }
404 span.red-background { background: red; }
405 span.silver-background { background: silver; }
406 span.teal-background { background: teal; }
407 span.white-background { background: white; }
408 span.yellow-background { background: yellow; }
410 span.big { font-size:
2em; }
411 span.small { font-size:
0.6em; }
413 span.underline { text-decoration: underline; }
414 span.overline { text-decoration: overline; }
415 span.line-through { text-decoration: line-through; }
417 div.unbreakable { page-break-inside: avoid; }
427 margin-bottom:
1.5em;
429 div.tableblock
> table {
430 border:
3px solid #
527bbd;
432 thead, p.table.header {
439 /* Because the table frame attribute is overridden by CSS in most browsers. */
440 div.tableblock
> table[
frame=
"void"] {
443 div.tableblock
> table[
frame=
"hsides"] {
444 border-left-style: none;
445 border-right-style: none;
447 div.tableblock
> table[
frame=
"vsides"] {
448 border-top-style: none;
449 border-bottom-style: none;
460 margin-bottom:
1.5em;
462 thead, p.tableblock.header {
473 border-color: #
527bbd;
474 border-collapse: collapse;
476 th.tableblock, td.tableblock {
480 border-color: #
527bbd;
483 table.tableblock.frame-topbot {
484 border-left-style: hidden;
485 border-right-style: hidden;
487 table.tableblock.frame-sides {
488 border-top-style: hidden;
489 border-bottom-style: hidden;
491 table.tableblock.frame-none {
492 border-style: hidden;
495 th.tableblock.halign-left, td.tableblock.halign-left {
498 th.tableblock.halign-center, td.tableblock.halign-center {
501 th.tableblock.halign-right, td.tableblock.halign-right {
505 th.tableblock.valign-top, td.tableblock.valign-top {
508 th.tableblock.valign-middle, td.tableblock.valign-middle {
509 vertical-align: middle;
511 th.tableblock.valign-bottom, td.tableblock.valign-bottom {
512 vertical-align: bottom;
523 padding-bottom:
0.5em;
524 border-top:
2px solid silver;
525 border-bottom:
2px solid silver;
530 body.manpage div.sectionbody {
535 body.manpage div#toc { display: none; }
540 <script type=
"text/javascript">
542 var asciidoc = { // Namespace.
544 /////////////////////////////////////////////////////////////////////
545 // Table Of Contents generator
546 /////////////////////////////////////////////////////////////////////
548 /* Author: Mihai Bazon, September
2002
549 * http://students.infoiasi.ro/~mishoo
551 * Table Of Content generator
554 * Feel free to use this script under the terms of the GNU General Public
555 * License, as long as you do not remove or alter this notice.
558 /* modified by Troy D. Hanson, September
2006. License: GPL */
559 /* modified by Stuart Rackham,
2006,
2009. License: GPL */
562 toc: function (toclevels) {
564 function getText(el) {
566 for (var i = el.firstChild; i != null; i = i.nextSibling) {
567 if (i.nodeType ==
3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
569 else if (i.firstChild != null)
575 function TocEntry(el, text, toclevel) {
578 this.toclevel = toclevel;
581 function tocEntries(el, toclevels) {
582 var result = new Array;
583 var re = new RegExp('[hH]([
1-'+(toclevels+
1)+'])');
584 // Function that scans the DOM tree for header elements (the DOM2
585 // nodeIterator API would be a better technique but not supported by all
587 var iterate = function (el) {
588 for (var i = el.firstChild; i != null; i = i.nextSibling) {
589 if (i.nodeType ==
1 /* Node.ELEMENT_NODE */) {
590 var mo = re.exec(i.tagName);
591 if (mo && (i.getAttribute(
"class") || i.getAttribute(
"className")) !=
"float") {
592 result[result.length] = new TocEntry(i, getText(i), mo[
1]-
1);
602 var toc = document.getElementById(
"toc");
607 // Delete existing TOC entries in case we're reloading the TOC.
608 var tocEntriesToRemove = [];
610 for (i =
0; i < toc.childNodes.length; i++) {
611 var entry = toc.childNodes[i];
612 if (entry.nodeName.toLowerCase() == 'div'
613 && entry.getAttribute(
"class")
614 && entry.getAttribute(
"class").match(/^toclevel/))
615 tocEntriesToRemove.push(entry);
617 for (i =
0; i < tocEntriesToRemove.length; i++) {
618 toc.removeChild(tocEntriesToRemove[i]);
621 // Rebuild TOC entries.
622 var entries = tocEntries(document.getElementById(
"content"), toclevels);
623 for (var i =
0; i < entries.length; ++i) {
624 var entry = entries[i];
625 if (entry.element.id ==
"")
626 entry.element.id =
"_toc_" + i;
627 var a = document.createElement(
"a");
628 a.href =
"#" + entry.element.id;
629 a.appendChild(document.createTextNode(entry.text));
630 var div = document.createElement(
"div");
632 div.className =
"toclevel" + entry.toclevel;
633 toc.appendChild(div);
635 if (entries.length ==
0)
636 toc.parentNode.removeChild(toc);
640 /////////////////////////////////////////////////////////////////////
641 // Footnotes generator
642 /////////////////////////////////////////////////////////////////////
644 /* Based on footnote generation code from:
645 * http://www.brandspankingnew.net/archive/
2005/
07/format_footnote.html
648 footnotes: function () {
649 // Delete existing footnote entries in case we're reloading the footnodes.
651 var noteholder = document.getElementById(
"footnotes");
655 var entriesToRemove = [];
656 for (i =
0; i < noteholder.childNodes.length; i++) {
657 var entry = noteholder.childNodes[i];
658 if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute(
"class") ==
"footnote")
659 entriesToRemove.push(entry);
661 for (i =
0; i < entriesToRemove.length; i++) {
662 noteholder.removeChild(entriesToRemove[i]);
665 // Rebuild footnote entries.
666 var cont = document.getElementById(
"content");
667 var spans = cont.getElementsByTagName(
"span");
670 for (i=
0; i
<spans.length; i++) {
671 if (spans[i].className ==
"footnote") {
673 var note = spans[i].getAttribute(
"data-note");
675 // Use [\s\S] in place of . so multi-line matches work.
676 // Because JavaScript has no s (dotall) regex flag.
677 note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[
1];
679 "[<a id='_footnoteref_" + n +
"' href='#_footnote_" + n +
680 "' title='View footnote' class='footnote'>" + n +
"</a>]";
681 spans[i].setAttribute(
"data-note", note);
683 noteholder.innerHTML +=
684 "<div class='footnote' id='_footnote_" + n +
"'>" +
685 "<a href='#_footnoteref_" + n +
"' title='Return to text'>" +
686 n +
"</a>. " + note +
"</div>";
687 var id =spans[i].getAttribute(
"id");
688 if (id != null) refs[
"#"+id] = n;
692 noteholder.parentNode.removeChild(noteholder);
694 // Process footnoterefs.
695 for (i=
0; i
<spans.length; i++) {
696 if (spans[i].className ==
"footnoteref") {
697 var href = spans[i].getElementsByTagName(
"a")[
0].getAttribute(
"href");
698 href = href.match(/#.*/)[
0]; // Because IE return full URL.
701 "[<a href='#_footnote_" + n +
702 "' title='View footnote' class='footnote'>" + n +
"</a>]";
708 install: function(toclevels) {
711 function reinstall() {
712 asciidoc.footnotes();
714 asciidoc.toc(toclevels);
718 function reinstallAndRemoveTimer() {
719 clearInterval(timerId);
723 timerId = setInterval(reinstall,
500);
724 if (document.addEventListener)
725 document.addEventListener(
"DOMContentLoaded", reinstallAndRemoveTimer, false);
727 window.onload = reinstallAndRemoveTimer;
735 <body class=
"manpage">
738 gitcli(
7) Manual Page
741 <div class=
"sectionbody">
743 Git command-line interface and conventions
749 <h2 id=
"_synopsis">SYNOPSIS
</h2>
750 <div class=
"sectionbody">
751 <div class=
"paragraph"><p>gitcli
</p></div>
755 <h2 id=
"_description">DESCRIPTION
</h2>
756 <div class=
"sectionbody">
757 <div class=
"paragraph"><p>This manual describes the convention used throughout Git CLI.
</p></div>
758 <div class=
"paragraph"><p>Many commands take revisions (most often
"commits", but sometimes
759 "tree-ish", depending on the context and command) and paths as their
760 arguments. Here are the rules:
</p></div>
761 <div class=
"ulist"><ul>
764 Options come first and then args.
765 A subcommand may take dashed options (which may take their own
766 arguments, e.g.
"--max-parents 2") and arguments. You SHOULD
767 give dashed options first and then arguments. Some commands may
768 accept dashed options after you have already gave non-option
769 arguments (which may make the command ambiguous), but you should
770 not rely on it (because eventually we may find a way to fix
771 these ambiguity by enforcing the
"options then args" rule).
776 Revisions come first and then paths.
777 E.g. in
<code>git diff v1.0 v2.0 arch/x86 include/asm-x86
</code>,
778 <code>v1.0
</code> and
<code>v2.0
</code> are revisions and
<code>arch/x86
</code> and
<code>include/asm-x86
</code>
784 When an argument can be misunderstood as either a revision or a path,
785 they can be disambiguated by placing
<code>--
</code> between them.
786 E.g.
<code>git diff -- HEAD
</code> is,
"I have a file called HEAD in my work
787 tree. Please show changes between the version I staged in the index
788 and what I have in the work tree for that file", not
"show difference
789 between the HEAD commit and the work tree as a whole". You can say
790 <code>git diff HEAD --
</code> to ask for the latter.
795 Without disambiguating
<code>--
</code>, Git makes a reasonable guess, but errors
796 out and asking you to disambiguate when ambiguous. E.g. if you have a
797 file called HEAD in your work tree,
<code>git diff HEAD
</code> is ambiguous, and
798 you have to say either
<code>git diff HEAD --
</code> or
<code>git diff -- HEAD
</code> to
804 Because
<code>--
</code> disambiguates revisions and paths in some commands, it
805 cannot be used for those commands to separate options and revisions.
806 You can use
<code>--end-of-options
</code> for this (it also works for commands
807 that do not distinguish between revisions in paths, in which case it
808 is simply an alias for
<code>--
</code>).
810 <div class=
"paragraph"><p>When writing a script that is expected to handle random user-input, it is
811 a good practice to make it explicit which arguments are which by placing
812 disambiguating
<code>--
</code> at appropriate places.
</p></div>
816 Many commands allow wildcards in paths, but you need to protect
817 them from getting globbed by the shell. These two mean different
820 <div class=
"listingblock">
821 <div class=
"content">
822 <pre><code>$ git restore *.c
823 $ git restore \*.c
</code></pre>
825 <div class=
"paragraph"><p>The former lets your shell expand the fileglob, and you are asking
826 the dot-C files in your working tree to be overwritten with the version
827 in the index. The latter passes the
<code>*.c
</code> to Git, and you are asking
828 the paths in the index that match the pattern to be checked out to your
829 working tree. After running
<code>git add hello.c; rm hello.c
</code>, you will
<em>not
</em>
830 see
<code>hello.c
</code> in your working tree with the former, but with the latter
835 Just as the filesystem
<em>.
</em> (period) refers to the current directory,
836 using a
<em>.
</em> as a repository name in Git (a dot-repository) is a relative
837 path and means your current repository.
841 <div class=
"paragraph"><p>Here are the rules regarding the
"flags" that you should follow when you are
842 scripting Git:
</p></div>
843 <div class=
"ulist"><ul>
846 It
’s preferred to use the non-dashed form of Git commands, which means that
847 you should prefer
<code>git foo
</code> to
<code>git-foo
</code>.
852 Splitting short options to separate words (prefer
<code>git foo -a -b
</code>
853 to
<code>git foo -ab
</code>, the latter may not even work).
858 When a command-line option takes an argument, use the
<em>stuck
</em> form. In
859 other words, write
<code>git foo -oArg
</code> instead of
<code>git foo -o Arg
</code> for short
860 options, and
<code>git foo --long-opt=Arg
</code> instead of
<code>git foo --long-opt Arg
</code>
861 for long options. An option that takes optional option-argument must be
862 written in the
<em>stuck
</em> form.
867 When you give a revision parameter to a command, make sure the parameter is
868 not ambiguous with a name of a file in the work tree. E.g. do not write
869 <code>git log -
1 HEAD
</code> but write
<code>git log -
1 HEAD --
</code>; the former will not work
870 if you happen to have a file called
<code>HEAD
</code> in the work tree.
875 Many commands allow a long option
<code>--option
</code> to be abbreviated
876 only to their unique prefix (e.g. if there is no other option
877 whose name begins with
<code>opt
</code>, you may be able to spell
<code>--opt
</code> to
878 invoke the
<code>--option
</code> flag), but you should fully spell them out
879 when writing your scripts; later versions of Git may introduce a
880 new option whose name shares the same prefix, e.g.
<code>--optimize
</code>,
881 to make a short prefix that used to be unique no longer unique.
888 <h2 id=
"_enhanced_option_parser">ENHANCED OPTION PARSER
</h2>
889 <div class=
"sectionbody">
890 <div class=
"paragraph"><p>From the Git
1.5.4 series and further, many Git commands (not all of them at the
891 time of the writing though) come with an enhanced option parser.
</p></div>
892 <div class=
"paragraph"><p>Here is a list of the facilities provided by this option parser.
</p></div>
894 <h3 id=
"_magic_options">Magic Options
</h3>
895 <div class=
"paragraph"><p>Commands which have the enhanced option parser activated all understand a
896 couple of magic command-line options:
</p></div>
897 <div class=
"dlist"><dl>
903 gives a pretty printed usage of the command.
905 <div class=
"listingblock">
906 <div class=
"content">
907 <pre><code>$ git describe -h
908 usage: git describe [
<options
>]
<commit-ish
>*
909 or: git describe [
<options
>] --dirty
911 --contains find the tag that comes after the commit
912 --debug debug search strategy on stderr
914 --tags use any tag, even unannotated
915 --long always use long format
916 --abbrev[=
<n
>] use
<n
> digits to display SHA-
1s
</code></pre>
918 <div class=
"paragraph"><p>Note that some subcommand (e.g.
<code>git grep
</code>) may behave differently
919 when there are things on the command line other than
<code>-h
</code>, but
<code>git
920 subcmd -h
</code> without anything else on the command line is meant to
921 consistently give the usage.
</p></div>
928 Some Git commands take options that are only used for plumbing or that
929 are deprecated, and such options are hidden from the default usage. This
930 option gives the full list of options.
936 <h3 id=
"_negating_options">Negating options
</h3>
937 <div class=
"paragraph"><p>Options with long option names can be negated by prefixing
<code>--no-
</code>. For
938 example,
<code>git branch
</code> has the option
<code>--track
</code> which is
<em>on
</em> by default. You
939 can use
<code>--no-track
</code> to override that behaviour. The same goes for
<code>--color
</code>
940 and
<code>--no-color
</code>.
</p></div>
943 <h3 id=
"_aggregating_short_options">Aggregating short options
</h3>
944 <div class=
"paragraph"><p>Commands that support the enhanced option parser allow you to aggregate short
945 options. This means that you can for example use
<code>git rm -rf
</code> or
946 <code>git clean -fdx
</code>.
</p></div>
949 <h3 id=
"_abbreviating_long_options">Abbreviating long options
</h3>
950 <div class=
"paragraph"><p>Commands that support the enhanced option parser accepts unique
951 prefix of a long option as if it is fully spelled out, but use this
952 with a caution. For example,
<code>git commit --amen
</code> behaves as if you
953 typed
<code>git commit --amend
</code>, but that is true only until a later version
954 of Git introduces another option that shares the same prefix,
955 e.g.
<code>git commit --amenity
</code> option.
</p></div>
958 <h3 id=
"_separating_argument_from_the_option">Separating argument from the option
</h3>
959 <div class=
"paragraph"><p>You can write the mandatory option parameter to an option as a separate
960 word on the command line. That means that all the following uses work:
</p></div>
961 <div class=
"listingblock">
962 <div class=
"content">
963 <pre><code>$ git foo --long-opt=Arg
964 $ git foo --long-opt Arg
966 $ git foo -o Arg
</code></pre>
968 <div class=
"paragraph"><p>However, this is
<strong>NOT
</strong> allowed for switches with an optional value, where the
969 <em>stuck
</em> form must be used:
</p></div>
970 <div class=
"listingblock">
971 <div class=
"content">
972 <pre><code>$ git describe --abbrev HEAD # correct
973 $ git describe --abbrev=
10 HEAD # correct
974 $ git describe --abbrev
10 HEAD # NOT WHAT YOU MEANT
</code></pre>
980 <h2 id=
"_notes_on_frequently_confused_options">NOTES ON FREQUENTLY CONFUSED OPTIONS
</h2>
981 <div class=
"sectionbody">
982 <div class=
"paragraph"><p>Many commands that can work on files in the working tree
983 and/or in the index can take
<code>--cached
</code> and/or
<code>--index
</code>
984 options. Sometimes people incorrectly think that, because
985 the index was originally called cache, these two are
986 synonyms. They are
<strong>not
</strong> — these two options mean very
987 different things.
</p></div>
988 <div class=
"ulist"><ul>
991 The
<code>--cached
</code> option is used to ask a command that
992 usually works on files in the working tree to
<strong>only
</strong> work
993 with the index. For example,
<code>git grep
</code>, when used
994 without a commit to specify from which commit to look for
995 strings in, usually works on files in the working tree,
996 but with the
<code>--cached
</code> option, it looks for strings in
1002 The
<code>--index
</code> option is used to ask a command that
1003 usually works on files in the working tree to
<strong>also
</strong>
1004 affect the index. For example,
<code>git stash apply
</code> usually
1005 merges changes recorded in a stash entry to the working tree,
1006 but with the
<code>--index
</code> option, it also merges changes to
1011 <div class=
"paragraph"><p><code>git apply
</code> command can be used with
<code>--cached
</code> and
1012 <code>--index
</code> (but not at the same time). Usually the command
1013 only affects the files in the working tree, but with
1014 <code>--index
</code>, it patches both the files and their index
1015 entries, and with
<code>--cached
</code>, it modifies only the index
1017 <div class=
"paragraph"><p>See also
<a href=
"https://lore.kernel.org/git/7v64clg5u9.fsf@assigned-by-dhcp.cox.net/">https://lore.kernel.org/git/
7v64clg5u9.fsf@assigned-by-dhcp.cox.net/
</a> and
1018 <a href=
"https://lore.kernel.org/git/7vy7ej9g38.fsf@gitster.siamese.dyndns.org/">https://lore.kernel.org/git/
7vy7ej9g38.fsf@gitster.siamese.dyndns.org/
</a> for further
1019 information.
</p></div>
1020 <div class=
"paragraph"><p>Some other commands that also work on files in the working tree and/or
1021 in the index can take
<code>--staged
</code> and/or
<code>--worktree
</code>.
</p></div>
1022 <div class=
"ulist"><ul>
1025 <code>--staged
</code> is exactly like
<code>--cached
</code>, which is used to ask a
1026 command to only work on the index, not the working tree.
1031 <code>--worktree
</code> is the opposite, to ask a command to work on the
1032 working tree only, not the index.
1037 The two options can be specified together to ask a command to work
1038 on both the index and the working tree.
1045 <h2 id=
"_git">GIT
</h2>
1046 <div class=
"sectionbody">
1047 <div class=
"paragraph"><p>Part of the
<a href=
"git.html">git(
1)
</a> suite
</p></div>
1051 <div id=
"footnotes"><hr /></div>
1053 <div id=
"footer-text">
1055 2022-
02-
16 17:
29:
08 PST