Gecko [ www.satitravel.com ]

Name	Size	Permission	Date
RelNotes	[ DIR ]	drwxr-xr-x	2026-06-10 18:39
contrib	[ DIR ]	drwxr-xr-x	2026-06-10 18:39
howto	[ DIR ]	drwxr-xr-x	2026-06-10 18:39
technical	[ DIR ]	drwxr-xr-x	2026-06-10 18:39
CODE_OF_CONDUCT.md	5.85 KB	-rw-r--r--	2025-06-13 22:14
MyFirstContribution.html	88.45 KB	-rw-r--r--	2025-07-22 14:31
MyFirstContribution.txt	53.32 KB	-rw-r--r--	2025-06-13 22:14
MyFirstObjectWalk.html	59.13 KB	-rw-r--r--	2025-07-22 14:31
MyFirstObjectWalk.txt	28.3 KB	-rw-r--r--	2025-06-13 22:14
README.md	3.57 KB	-rw-r--r--	2025-06-13 22:14
ReviewingGuidelines.html	26.2 KB	-rw-r--r--	2025-07-22 14:31
ReviewingGuidelines.txt	7.91 KB	-rw-r--r--	2025-06-13 22:14
SubmittingPatches.html	54.36 KB	-rw-r--r--	2025-07-22 14:32
SubmittingPatches.txt	29.44 KB	-rw-r--r--	2025-07-22 14:31
ToolsForGit.html	18.57 KB	-rw-r--r--	2025-07-22 14:31
ToolsForGit.txt	1.32 KB	-rw-r--r--	2025-06-13 22:14
blame-options.txt	5.86 KB	-rw-r--r--	2025-06-13 22:14
cmds-ancillaryinterrogators.txt	1.26 KB	-rw-r--r--	2025-07-22 14:30
cmds-ancillarymanipulators.txt	746 B	-rw-r--r--	2025-07-22 14:30
cmds-developerinterfaces.txt	678 B	-rw-r--r--	2025-07-22 14:30
cmds-foreignscminterface.txt	399 B	-rw-r--r--	2025-07-22 14:30
cmds-guide.txt	833 B	-rw-r--r--	2025-07-22 14:30
cmds-mainporcelain.txt	2.96 KB	-rw-r--r--	2025-07-22 14:30
cmds-plumbinginterrogators.txt	1.5 KB	-rw-r--r--	2025-07-22 14:30
cmds-plumbingmanipulators.txt	1.38 KB	-rw-r--r--	2025-07-22 14:30
cmds-purehelpers.txt	1.24 KB	-rw-r--r--	2025-07-22 14:30
cmds-synchelpers.txt	449 B	-rw-r--r--	2025-07-22 14:30
cmds-synchingrepositories.txt	397 B	-rw-r--r--	2025-07-22 14:30
cmds-userinterfaces.txt	507 B	-rw-r--r--	2025-07-22 14:30
config.txt	17.58 KB	-rw-r--r--	2025-07-22 14:30
date-formats.txt	1.14 KB	-rw-r--r--	2025-06-13 22:14
diff-format.txt	6.42 KB	-rw-r--r--	2025-06-13 22:14
diff-generate-patch.txt	7.08 KB	-rw-r--r--	2025-06-13 22:14
diff-options.txt	31.68 KB	-rw-r--r--	2025-06-13 22:14
docbook-xsl.css	4.45 KB	-rw-r--r--	2025-06-13 22:14
everyday.html	16.6 KB	-rw-r--r--	2025-07-22 14:31
fetch-options.txt	11.99 KB	-rw-r--r--	2025-06-13 22:14
fsck-msgids.txt	4.1 KB	-rw-r--r--	2025-06-13 22:14
git-add.html	39.42 KB	-rw-r--r--	2025-07-22 14:32
git-add.txt	15.79 KB	-rw-r--r--	2025-06-13 22:14
git-am.html	32.38 KB	-rw-r--r--	2025-07-22 14:31
git-am.txt	9.1 KB	-rw-r--r--	2025-06-13 22:14
git-annotate.html	27.73 KB	-rw-r--r--	2025-07-22 14:31
git-annotate.txt	771 B	-rw-r--r--	2025-06-13 22:14
git-apply.html	32.62 KB	-rw-r--r--	2025-07-22 14:31
git-apply.txt	10.69 KB	-rw-r--r--	2025-06-13 22:14
git-archive.html	29.16 KB	-rw-r--r--	2025-07-22 14:31
git-archive.txt	8.29 KB	-rw-r--r--	2025-06-13 22:14
git-bisect-lk2009.html	79.34 KB	-rw-r--r--	2025-07-22 14:30
git-bisect-lk2009.txt	48.53 KB	-rw-r--r--	2025-06-13 22:14
git-bisect.html	39.62 KB	-rw-r--r--	2025-07-22 14:32
git-bisect.txt	17.49 KB	-rw-r--r--	2025-06-13 22:14
git-blame.html	41.5 KB	-rw-r--r--	2025-07-22 14:31
git-blame.txt	8.53 KB	-rw-r--r--	2025-06-13 22:14
git-branch.html	47.12 KB	-rw-r--r--	2025-07-22 14:32
git-branch.txt	15.38 KB	-rw-r--r--	2025-06-13 22:14
git-bugreport.html	20.03 KB	-rw-r--r--	2025-07-22 14:32
git-bugreport.txt	2.36 KB	-rw-r--r--	2025-06-13 22:14
git-bundle.html	32.49 KB	-rw-r--r--	2025-07-22 14:32
git-bundle.txt	11.43 KB	-rw-r--r--	2025-06-13 22:14
git-cat-file.html	37.75 KB	-rw-r--r--	2025-07-22 14:31
git-cat-file.txt	13.3 KB	-rw-r--r--	2025-06-13 22:14
git-check-attr.html	22.1 KB	-rw-r--r--	2025-07-22 14:32
git-check-attr.txt	3.31 KB	-rw-r--r--	2025-06-13 22:14
git-check-ignore.html	22.59 KB	-rw-r--r--	2025-07-22 14:32
git-check-ignore.txt	4.06 KB	-rw-r--r--	2025-06-13 22:14
git-check-mailmap.html	18.38 KB	-rw-r--r--	2025-07-22 14:31
git-check-mailmap.txt	1.08 KB	-rw-r--r--	2025-06-13 22:14
git-check-ref-format.html	23.48 KB	-rw-r--r--	2025-07-22 14:31
git-check-ref-format.txt	4.92 KB	-rw-r--r--	2025-06-13 22:14
git-checkout-index.html	24.77 KB	-rw-r--r--	2025-07-22 14:32
git-checkout-index.txt	5.54 KB	-rw-r--r--	2025-06-13 22:14
git-checkout.html	51.48 KB	-rw-r--r--	2025-07-22 14:32
git-checkout.txt	21.84 KB	-rw-r--r--	2025-06-13 22:14
git-cherry-pick.html	30.34 KB	-rw-r--r--	2025-07-22 14:32
git-cherry-pick.txt	8.56 KB	-rw-r--r--	2025-06-13 22:14
git-cherry.html	21.9 KB	-rw-r--r--	2025-07-22 14:31
git-cherry.txt	3.53 KB	-rw-r--r--	2025-06-13 22:14
git-clean.html	23.42 KB	-rw-r--r--	2025-07-22 14:32
git-clean.txt	4.42 KB	-rw-r--r--	2025-06-13 22:14
git-clone.html	43.29 KB	-rw-r--r--	2025-07-22 14:31
git-clone.txt	14.43 KB	-rw-r--r--	2025-06-13 22:14
git-column.html	22.77 KB	-rw-r--r--	2025-07-22 14:31
git-column.txt	2.15 KB	-rw-r--r--	2025-06-13 22:14
git-commit-graph.html	25.53 KB	-rw-r--r--	2025-07-22 14:31
git-commit-graph.txt	5.81 KB	-rw-r--r--	2025-06-13 22:14
git-commit-tree.html	26.06 KB	-rw-r--r--	2025-07-22 14:32
git-commit-tree.txt	2.65 KB	-rw-r--r--	2025-06-13 22:14
git-commit.html	55.81 KB	-rw-r--r--	2025-07-22 14:32
git-commit.txt	21.07 KB	-rw-r--r--	2025-06-13 22:14
git-config.html	405.8 KB	-rw-r--r--	2025-07-22 14:31
git-config.txt	19.29 KB	-rw-r--r--	2025-06-13 22:14
git-contacts.html	20.23 KB	-rw-r--r--	2025-07-22 14:31
git-contacts.txt	2.52 KB	-rw-r--r--	2025-06-13 22:14
git-count-objects.html	18.5 KB	-rw-r--r--	2025-07-22 14:32
git-count-objects.txt	1.32 KB	-rw-r--r--	2025-06-13 22:14
git-credential-cache--daemon.html	17.76 KB	-rw-r--r--	2025-07-22 14:32
git-credential-cache--daemon.txt	891 B	-rw-r--r--	2025-06-13 22:14
git-credential-cache.html	19.71 KB	-rw-r--r--	2025-07-22 14:31
git-credential-cache.txt	2.43 KB	-rw-r--r--	2025-06-13 22:14
git-credential-store.html	21.53 KB	-rw-r--r--	2025-07-22 14:32
git-credential-store.txt	3.55 KB	-rw-r--r--	2025-06-13 22:14
git-credential.html	26.05 KB	-rw-r--r--	2025-07-22 14:32
git-credential.txt	7.16 KB	-rw-r--r--	2025-06-13 22:14
git-describe.html	27.61 KB	-rw-r--r--	2025-07-22 14:32
git-describe.txt	8.12 KB	-rw-r--r--	2025-06-13 22:14
git-diagnose.html	19.68 KB	-rw-r--r--	2025-07-22 14:32
git-diagnose.txt	2.16 KB	-rw-r--r--	2025-06-13 22:14
git-diff-files.html	77.28 KB	-rw-r--r--	2025-07-22 14:32
git-diff-files.txt	1.2 KB	-rw-r--r--	2025-06-13 22:14
git-diff-index.html	82.37 KB	-rw-r--r--	2025-07-22 14:32
git-diff-index.txt	4.7 KB	-rw-r--r--	2025-06-13 22:14
git-diff-tree.html	113.33 KB	-rw-r--r--	2025-07-22 14:32
git-diff-tree.txt	4.09 KB	-rw-r--r--	2025-06-13 22:14
git-diff.html	104.58 KB	-rw-r--r--	2025-07-22 14:32
git-diff.txt	7.85 KB	-rw-r--r--	2025-06-13 22:14
git-difftool.html	26.41 KB	-rw-r--r--	2025-07-22 14:32
git-difftool.txt	4.52 KB	-rw-r--r--	2025-06-13 22:14
git-fast-export.html	30.91 KB	-rw-r--r--	2025-07-22 14:32
git-fast-export.txt	11.02 KB	-rw-r--r--	2025-06-13 22:14
git-fast-import.html	100.86 KB	-rw-r--r--	2025-07-22 14:32
git-fast-import.txt	58.56 KB	-rw-r--r--	2025-06-13 22:14
git-fetch-pack.html	22.71 KB	-rw-r--r--	2025-07-22 14:31
git-fetch-pack.txt	4.15 KB	-rw-r--r--	2025-06-13 22:14
git-fetch.html	73.69 KB	-rw-r--r--	2025-07-22 14:31
git-fetch.txt	11.54 KB	-rw-r--r--	2025-06-13 22:14
git-filter-branch.html	53.37 KB	-rw-r--r--	2025-07-22 14:32
git-filter-branch.txt	30.3 KB	-rw-r--r--	2025-06-13 22:14
git-fmt-merge-msg.html	20.93 KB	-rw-r--r--	2025-07-22 14:32
git-fmt-merge-msg.txt	1.89 KB	-rw-r--r--	2025-06-13 22:14
git-for-each-ref.html	42.42 KB	-rw-r--r--	2025-07-22 14:32
git-for-each-ref.txt	16.67 KB	-rw-r--r--	2025-06-13 22:14
git-for-each-repo.html	18.84 KB	-rw-r--r--	2025-07-22 14:31
git-for-each-repo.txt	1.51 KB	-rw-r--r--	2025-06-13 22:14
git-format-patch.html	79.92 KB	-rw-r--r--	2025-07-22 14:32
git-format-patch.txt	28.2 KB	-rw-r--r--	2025-06-13 22:14
git-fsck-objects.html	16.98 KB	-rw-r--r--	2025-07-22 14:32
git-fsck-objects.txt	354 B	-rw-r--r--	2025-06-13 22:14
git-fsck.html	38.24 KB	-rw-r--r--	2025-07-22 14:32
git-fsck.txt	5.74 KB	-rw-r--r--	2025-06-13 22:14
git-fsmonitor--daemon.html	22.34 KB	-rw-r--r--	2025-07-22 14:32
git-fsmonitor--daemon.txt	3.53 KB	-rw-r--r--	2025-06-13 22:14
git-gc.html	35.84 KB	-rw-r--r--	2025-07-22 14:32
git-gc.txt	6.14 KB	-rw-r--r--	2025-06-13 22:14
git-get-tar-commit-id.html	17.42 KB	-rw-r--r--	2025-07-22 14:32
git-get-tar-commit-id.txt	753 B	-rw-r--r--	2025-06-13 22:14
git-grep.html	35.19 KB	-rw-r--r--	2025-07-22 14:31
git-grep.txt	10.51 KB	-rw-r--r--	2025-06-13 22:14
git-hash-object.html	19.47 KB	-rw-r--r--	2025-07-22 14:32
git-hash-object.txt	2.09 KB	-rw-r--r--	2025-06-13 22:14
git-help.html	27.48 KB	-rw-r--r--	2025-07-22 14:32
git-help.txt	7.35 KB	-rw-r--r--	2025-06-13 22:14
git-hook.html	18.37 KB	-rw-r--r--	2025-07-22 14:31
git-hook.txt	1 KB	-rw-r--r--	2025-06-13 22:14
git-http-backend.html	30.25 KB	-rw-r--r--	2025-07-22 14:32
git-http-backend.txt	11.2 KB	-rw-r--r--	2025-06-13 22:14
git-http-fetch.html	19.22 KB	-rw-r--r--	2025-07-22 14:32
git-http-fetch.txt	1.73 KB	-rw-r--r--	2025-06-13 22:14
git-http-push.html	20.89 KB	-rw-r--r--	2025-07-22 14:32
git-http-push.txt	2.92 KB	-rw-r--r--	2025-06-13 22:14
git-imap-send.html	24.88 KB	-rw-r--r--	2025-07-22 14:32
git-imap-send.txt	3.48 KB	-rw-r--r--	2025-06-13 22:14
git-index-pack.html	24.16 KB	-rw-r--r--	2025-07-22 14:32
git-index-pack.txt	5.08 KB	-rw-r--r--	2025-06-13 22:14
git-init-db.html	17.05 KB	-rw-r--r--	2025-07-22 14:32
git-init-db.txt	409 B	-rw-r--r--	2025-06-13 22:14
git-init.html	25.98 KB	-rw-r--r--	2025-07-22 14:32
git-init.txt	5.73 KB	-rw-r--r--	2025-06-13 22:14
git-interpret-trailers.html	41.02 KB	-rw-r--r--	2025-07-22 14:32
git-interpret-trailers.txt	18.14 KB	-rw-r--r--	2025-06-13 22:14
git-log.html	178.21 KB	-rw-r--r--	2025-07-22 14:32
git-log.txt	6.7 KB	-rw-r--r--	2025-06-13 22:14
git-ls-files.html	34.23 KB	-rw-r--r--	2025-07-22 14:31
git-ls-files.txt	11.35 KB	-rw-r--r--	2025-06-13 22:14
git-ls-remote.html	23.78 KB	-rw-r--r--	2025-07-22 14:32
git-ls-remote.txt	4.73 KB	-rw-r--r--	2025-06-13 22:14
git-ls-tree.html	25.03 KB	-rw-r--r--	2025-07-22 14:31
git-ls-tree.txt	5.39 KB	-rw-r--r--	2025-06-13 22:14
git-mailinfo.html	22.85 KB	-rw-r--r--	2025-07-22 14:32
git-mailinfo.txt	3.78 KB	-rw-r--r--	2025-06-13 22:14
git-mailsplit.html	18.81 KB	-rw-r--r--	2025-07-22 14:31
git-mailsplit.txt	1.31 KB	-rw-r--r--	2025-06-13 22:14
git-maintenance.html	44.92 KB	-rw-r--r--	2025-07-22 14:31
git-maintenance.txt	18.46 KB	-rw-r--r--	2025-06-13 22:14
git-merge-base.html	27.71 KB	-rw-r--r--	2025-07-22 14:31
git-merge-base.txt	7.58 KB	-rw-r--r--	2025-06-13 22:14
git-merge-file.html	22.13 KB	-rw-r--r--	2025-07-22 14:32
git-merge-file.txt	3.63 KB	-rw-r--r--	2025-06-13 22:14
git-merge-index.html	19.97 KB	-rw-r--r--	2025-07-22 14:32
git-merge-index.txt	2.39 KB	-rw-r--r--	2025-06-13 22:14
git-merge-one-file.html	17.01 KB	-rw-r--r--	2025-07-22 14:32
git-merge-one-file.txt	387 B	-rw-r--r--	2025-06-13 22:14
git-merge-tree.html	32.71 KB	-rw-r--r--	2025-07-22 14:32
git-merge-tree.txt	11.64 KB	-rw-r--r--	2025-06-13 22:14
git-merge.html	69.34 KB	-rw-r--r--	2025-07-22 14:31
git-merge.txt	14.71 KB	-rw-r--r--	2025-06-13 22:14
git-mergetool--lib.html	18.68 KB	-rw-r--r--	2025-07-22 14:31
git-mergetool--lib.txt	1.43 KB	-rw-r--r--	2025-06-13 22:14
git-mergetool.html	38.86 KB	-rw-r--r--	2025-07-22 14:31
git-mergetool.txt	4.37 KB	-rw-r--r--	2025-06-13 22:14
git-mktag.html	19.35 KB	-rw-r--r--	2025-07-22 14:32
git-mktag.txt	1.74 KB	-rw-r--r--	2025-06-13 22:14
git-mktree.html	18.04 KB	-rw-r--r--	2025-07-22 14:31
git-mktree.txt	1.05 KB	-rw-r--r--	2025-06-13 22:14
git-multi-pack-index.html	23.04 KB	-rw-r--r--	2025-07-22 14:32
git-multi-pack-index.txt	4.52 KB	-rw-r--r--	2025-06-13 22:14
git-mv.html	19.62 KB	-rw-r--r--	2025-07-22 14:31
git-mv.txt	2.05 KB	-rw-r--r--	2025-06-13 22:14
git-name-rev.html	21.16 KB	-rw-r--r--	2025-07-22 14:31
git-name-rev.txt	3.27 KB	-rw-r--r--	2025-06-13 22:14
git-notes.html	40.08 KB	-rw-r--r--	2025-07-22 14:32
git-notes.txt	13.54 KB	-rw-r--r--	2025-06-13 22:14
git-pack-objects.html	41.4 KB	-rw-r--r--	2025-07-22 14:32
git-pack-objects.txt	18.84 KB	-rw-r--r--	2025-06-13 22:14
git-pack-redundant.html	19.33 KB	-rw-r--r--	2025-07-22 14:32
git-pack-redundant.txt	1.83 KB	-rw-r--r--	2025-06-13 22:14
git-pack-refs.html	20.63 KB	-rw-r--r--	2025-07-22 14:31
git-pack-refs.txt	3.06 KB	-rw-r--r--	2025-06-13 22:14
git-patch-id.html	19.88 KB	-rw-r--r--	2025-07-22 14:32
git-patch-id.txt	2.37 KB	-rw-r--r--	2025-06-13 22:14
git-prune-packed.html	18.1 KB	-rw-r--r--	2025-07-22 14:31
git-prune-packed.txt	946 B	-rw-r--r--	2025-06-13 22:14
git-prune.html	19.85 KB	-rw-r--r--	2025-07-22 14:32
git-prune.txt	1.87 KB	-rw-r--r--	2025-06-13 22:14
git-pull.html	75.26 KB	-rw-r--r--	2025-07-22 14:32
git-pull.txt	8.16 KB	-rw-r--r--	2025-06-13 22:14
git-push.html	73.24 KB	-rw-r--r--	2025-07-22 14:31
git-push.txt	27.4 KB	-rw-r--r--	2025-06-13 22:14
git-quiltimport.html	19.01 KB	-rw-r--r--	2025-07-22 14:32
git-quiltimport.txt	1.65 KB	-rw-r--r--	2025-06-13 22:14
git-range-diff.html	30.93 KB	-rw-r--r--	2025-07-22 14:31
git-range-diff.txt	10.09 KB	-rw-r--r--	2025-06-13 22:14
git-read-tree.html	38.16 KB	-rw-r--r--	2025-07-22 14:31
git-read-tree.txt	16.5 KB	-rw-r--r--	2025-06-13 22:14
git-rebase.html	96.63 KB	-rw-r--r--	2025-07-22 14:31
git-rebase.txt	46.12 KB	-rw-r--r--	2025-06-13 22:14
git-receive-pack.html	29.73 KB	-rw-r--r--	2025-07-22 14:32
git-receive-pack.txt	9.3 KB	-rw-r--r--	2025-06-13 22:14
git-reflog.html	22.96 KB	-rw-r--r--	2025-07-22 14:32
git-reflog.txt	4.47 KB	-rw-r--r--	2025-06-13 22:14
git-remote-ext.html	22.47 KB	-rw-r--r--	2025-07-22 14:32
git-remote-ext.txt	3.88 KB	-rw-r--r--	2025-06-13 22:14
git-remote-fd.html	19.04 KB	-rw-r--r--	2025-07-22 14:32
git-remote-fd.txt	1.59 KB	-rw-r--r--	2025-06-13 22:14
git-remote-helpers.html	16.58 KB	-rw-r--r--	2025-07-22 14:31
git-remote.html	29.2 KB	-rw-r--r--	2025-07-22 14:32
git-remote.txt	8.56 KB	-rw-r--r--	2025-06-13 22:14
git-repack.html	32.05 KB	-rw-r--r--	2025-07-22 14:32
git-repack.txt	10.76 KB	-rw-r--r--	2025-06-13 22:14
git-replace.html	24.28 KB	-rw-r--r--	2025-07-22 14:32
git-replace.txt	5.09 KB	-rw-r--r--	2025-06-13 22:14
git-request-pull.html	19.82 KB	-rw-r--r--	2025-07-22 14:31
git-request-pull.txt	1.99 KB	-rw-r--r--	2025-06-13 22:14
git-rerere.html	26.41 KB	-rw-r--r--	2025-07-22 14:31
git-rerere.txt	7.6 KB	-rw-r--r--	2025-06-13 22:14
git-reset.html	43.48 KB	-rw-r--r--	2025-07-22 14:31
git-reset.txt	18.68 KB	-rw-r--r--	2025-06-13 22:14
git-restore.html	27.51 KB	-rw-r--r--	2025-07-22 14:31
git-restore.txt	6.92 KB	-rw-r--r--	2025-06-13 22:14
git-rev-list.html	115.36 KB	-rw-r--r--	2025-07-22 14:32
git-rev-list.txt	3.14 KB	-rw-r--r--	2025-06-13 22:14
git-rev-parse.html	63.13 KB	-rw-r--r--	2025-07-22 14:32
git-rev-parse.txt	15.47 KB	-rw-r--r--	2025-06-13 22:14
git-revert.html	26.16 KB	-rw-r--r--	2025-07-22 14:32
git-revert.txt	5.29 KB	-rw-r--r--	2025-06-13 22:14
git-rm.html	26.94 KB	-rw-r--r--	2025-07-22 14:31
git-rm.txt	7.07 KB	-rw-r--r--	2025-06-13 22:14
git-send-pack.html	24 KB	-rw-r--r--	2025-07-22 14:31
git-send-pack.txt	5.04 KB	-rw-r--r--	2025-06-13 22:14
git-sh-i18n--envsubst.html	17.74 KB	-rw-r--r--	2025-07-22 14:32
git-sh-i18n--envsubst.txt	928 B	-rw-r--r--	2025-06-13 22:14
git-sh-i18n.html	18.16 KB	-rw-r--r--	2025-07-22 14:32
git-sh-i18n.txt	1.12 KB	-rw-r--r--	2025-06-13 22:14
git-sh-setup.html	20.78 KB	-rw-r--r--	2025-07-22 14:32
git-sh-setup.txt	2.91 KB	-rw-r--r--	2025-06-13 22:14
git-shell.html	20.91 KB	-rw-r--r--	2025-07-22 14:32
git-shell.txt	2.91 KB	-rw-r--r--	2025-06-13 22:14
git-shortlog.html	63.1 KB	-rw-r--r--	2025-07-22 14:31
git-shortlog.txt	4.31 KB	-rw-r--r--	2025-06-13 22:14
git-show-branch.html	26.18 KB	-rw-r--r--	2025-07-22 14:32
git-show-branch.txt	6.43 KB	-rw-r--r--	2025-06-13 22:14
git-show-index.html	19.06 KB	-rw-r--r--	2025-07-22 14:32
git-show-index.txt	1.44 KB	-rw-r--r--	2025-06-13 22:14
git-show-ref.html	25.46 KB	-rw-r--r--	2025-07-22 14:32
git-show-ref.txt	6.49 KB	-rw-r--r--	2025-06-13 22:14
git-show.html	109.03 KB	-rw-r--r--	2025-07-22 14:32
git-show.txt	1.88 KB	-rw-r--r--	2025-06-13 22:14
git-sparse-checkout.html	42.92 KB	-rw-r--r--	2025-07-22 14:32
git-sparse-checkout.txt	20.76 KB	-rw-r--r--	2025-06-13 22:14
git-stage.html	16.93 KB	-rw-r--r--	2025-07-22 14:31
git-stage.txt	299 B	-rw-r--r--	2025-06-13 22:14
git-stash.html	37.69 KB	-rw-r--r--	2025-07-22 14:32
git-stash.txt	14.65 KB	-rw-r--r--	2025-06-13 22:14
git-status.html	44.65 KB	-rw-r--r--	2025-07-22 14:31
git-status.txt	19.82 KB	-rw-r--r--	2025-06-13 22:14
git-stripspace.html	19.55 KB	-rw-r--r--	2025-07-22 14:31
git-stripspace.txt	1.9 KB	-rw-r--r--	2025-06-13 22:14
git-submodule.html	44.51 KB	-rw-r--r--	2025-07-22 14:32
git-submodule.txt	20.33 KB	-rw-r--r--	2025-06-13 22:14
git-switch.html	32.53 KB	-rw-r--r--	2025-07-22 14:32
git-switch.txt	8.41 KB	-rw-r--r--	2025-06-13 22:14
git-symbolic-ref.html	19.97 KB	-rw-r--r--	2025-07-22 14:31
git-symbolic-ref.txt	2.27 KB	-rw-r--r--	2025-06-13 22:14
git-tag.html	38.04 KB	-rw-r--r--	2025-07-22 14:32
git-tag.txt	13.15 KB	-rw-r--r--	2025-06-13 22:14
git-tools.html	16.8 KB	-rw-r--r--	2025-07-22 14:30
git-tools.txt	422 B	-rw-r--r--	2025-06-13 22:14
git-unpack-file.html	17.23 KB	-rw-r--r--	2025-07-22 14:31
git-unpack-file.txt	434 B	-rw-r--r--	2025-06-13 22:14
git-unpack-objects.html	18.37 KB	-rw-r--r--	2025-07-22 14:32
git-unpack-objects.txt	1.19 KB	-rw-r--r--	2025-06-13 22:14
git-update-index.html	48.56 KB	-rw-r--r--	2025-07-22 14:31
git-update-index.txt	23.37 KB	-rw-r--r--	2025-06-13 22:14
git-update-ref.html	25.3 KB	-rw-r--r--	2025-07-22 14:31
git-update-ref.txt	6.15 KB	-rw-r--r--	2025-06-13 22:14
git-update-server-info.html	17.83 KB	-rw-r--r--	2025-07-22 14:32
git-update-server-info.txt	801 B	-rw-r--r--	2025-06-13 22:14
git-upload-archive.html	19.31 KB	-rw-r--r--	2025-07-22 14:32
git-upload-archive.txt	2.04 KB	-rw-r--r--	2025-06-13 22:14
git-upload-pack.html	21.16 KB	-rw-r--r--	2025-07-22 14:31
git-upload-pack.txt	2.93 KB	-rw-r--r--	2025-06-13 22:14
git-var.html	21.03 KB	-rw-r--r--	2025-07-22 14:32
git-var.txt	3.1 KB	-rw-r--r--	2025-06-13 22:14
git-verify-commit.html	17.53 KB	-rw-r--r--	2025-07-22 14:32
git-verify-commit.txt	575 B	-rw-r--r--	2025-06-13 22:14
git-verify-pack.html	18.51 KB	-rw-r--r--	2025-07-22 14:32
git-verify-pack.txt	1.08 KB	-rw-r--r--	2025-06-13 22:14
git-verify-tag.html	17.52 KB	-rw-r--r--	2025-07-22 14:31
git-verify-tag.txt	562 B	-rw-r--r--	2025-06-13 22:14
git-version.html	17.38 KB	-rw-r--r--	2025-07-22 14:31
git-version.txt	532 B	-rw-r--r--	2025-06-13 22:14
git-web--browse.html	21.88 KB	-rw-r--r--	2025-07-22 14:31
git-web--browse.txt	3.49 KB	-rw-r--r--	2025-06-13 22:14
git-whatchanged.html	18.14 KB	-rw-r--r--	2025-07-22 14:31
git-whatchanged.txt	1.07 KB	-rw-r--r--	2025-06-13 22:14
git-worktree.html	45.25 KB	-rw-r--r--	2025-07-22 14:32
git-worktree.txt	20.49 KB	-rw-r--r--	2025-06-13 22:14
git-write-tree.html	18.01 KB	-rw-r--r--	2025-07-22 14:32
git-write-tree.txt	1 KB	-rw-r--r--	2025-06-13 22:14
git.html	104.72 KB	-rw-r--r--	2025-07-22 14:32
git.txt	42.24 KB	-rw-r--r--	2025-06-13 22:14
gitattributes.html	80.9 KB	-rw-r--r--	2025-07-22 14:32
gitattributes.txt	48.35 KB	-rw-r--r--	2025-06-13 22:14
gitcli.html	28.89 KB	-rw-r--r--	2025-07-22 14:32
gitcli.txt	9.47 KB	-rw-r--r--	2025-06-13 22:14
gitcore-tutorial.html	97.79 KB	-rw-r--r--	2025-07-22 14:32
gitcore-tutorial.txt	60.78 KB	-rw-r--r--	2025-06-13 22:14
gitcredentials.html	31.23 KB	-rw-r--r--	2025-07-22 14:32
gitcredentials.txt	11.05 KB	-rw-r--r--	2025-06-13 22:14
gitdiffcore.html	32.95 KB	-rw-r--r--	2025-07-22 14:32
gitdiffcore.txt	13.75 KB	-rw-r--r--	2025-06-13 22:14
giteveryday.html	37.2 KB	-rw-r--r--	2025-07-22 14:32
giteveryday.txt	14.08 KB	-rw-r--r--	2025-06-13 22:14
gitfaq.html	43.05 KB	-rw-r--r--	2025-07-22 14:32
gitfaq.txt	20.58 KB	-rw-r--r--	2025-06-13 22:14
gitformat-bundle.html	20.94 KB	-rw-r--r--	2025-07-22 14:32
gitformat-bundle.txt	3.18 KB	-rw-r--r--	2025-06-13 22:14
gitformat-chunk.html	23.76 KB	-rw-r--r--	2025-07-22 14:32
gitformat-chunk.txt	5.43 KB	-rw-r--r--	2025-06-13 22:14
gitformat-commit-graph.html	27.96 KB	-rw-r--r--	2025-07-22 14:32
gitformat-commit-graph.txt	7.67 KB	-rw-r--r--	2025-06-13 22:14
gitformat-index.html	39.33 KB	-rw-r--r--	2025-07-22 14:32
gitformat-index.txt	14.82 KB	-rw-r--r--	2025-06-13 22:14
gitformat-pack.html	48.64 KB	-rw-r--r--	2025-07-22 14:32
gitformat-pack.txt	22.96 KB	-rw-r--r--	2025-06-13 22:14
gitformat-signature.html	26.72 KB	-rw-r--r--	2025-07-22 14:32
gitformat-signature.txt	7.9 KB	-rw-r--r--	2025-06-13 22:14
gitglossary.html	62.7 KB	-rw-r--r--	2025-07-22 14:32
gitglossary.txt	358 B	-rw-r--r--	2025-06-13 22:14
githooks.html	55.18 KB	-rw-r--r--	2025-07-22 14:32
githooks.txt	28.64 KB	-rw-r--r--	2025-06-13 22:14
gitignore.html	27.73 KB	-rw-r--r--	2025-07-22 14:32
gitignore.txt	8.71 KB	-rw-r--r--	2025-06-13 22:14
gitmailmap.html	22.28 KB	-rw-r--r--	2025-07-22 14:32
gitmailmap.txt	3.47 KB	-rw-r--r--	2025-06-13 22:14
gitmodules.html	23.49 KB	-rw-r--r--	2025-07-22 14:32
gitmodules.txt	4.69 KB	-rw-r--r--	2025-06-13 22:14
gitnamespaces.html	21.63 KB	-rw-r--r--	2025-07-22 14:32
gitnamespaces.txt	2.45 KB	-rw-r--r--	2025-06-13 22:14
gitprotocol-capabilities.html	36.55 KB	-rw-r--r--	2025-07-22 14:32
gitprotocol-capabilities.txt	14.95 KB	-rw-r--r--	2025-06-13 22:14
gitprotocol-common.html	21.06 KB	-rw-r--r--	2025-07-22 14:32
gitprotocol-common.txt	3.1 KB	-rw-r--r--	2025-06-13 22:14
gitprotocol-http.html	42.22 KB	-rw-r--r--	2025-07-22 14:32
gitprotocol-http.txt	17.57 KB	-rw-r--r--	2025-06-13 22:14
gitprotocol-pack.html	51.78 KB	-rw-r--r--	2025-07-22 14:32
gitprotocol-pack.txt	27.03 KB	-rw-r--r--	2025-06-13 22:14
gitprotocol-v2.html	58.29 KB	-rw-r--r--	2025-07-22 14:32
gitprotocol-v2.txt	30.7 KB	-rw-r--r--	2025-06-13 22:14
gitremote-helpers.html	47.08 KB	-rw-r--r--	2025-07-22 14:32
gitremote-helpers.txt	21.27 KB	-rw-r--r--	2025-06-13 22:14
gitrepository-layout.html	38.43 KB	-rw-r--r--	2025-07-22 14:32
gitrepository-layout.txt	11.35 KB	-rw-r--r--	2025-06-13 22:14
gitrevisions.html	40.65 KB	-rw-r--r--	2025-07-22 14:32
gitrevisions.txt	823 B	-rw-r--r--	2025-06-13 22:14
gitsubmodules.html	30.96 KB	-rw-r--r--	2025-07-22 14:32
gitsubmodules.txt	10.12 KB	-rw-r--r--	2025-06-13 22:14
gittutorial-2.html	33.74 KB	-rw-r--r--	2025-07-22 14:32
gittutorial-2.txt	14.4 KB	-rw-r--r--	2025-06-13 22:14
gittutorial.html	45.18 KB	-rw-r--r--	2025-07-22 14:32
gittutorial.txt	22.43 KB	-rw-r--r--	2025-06-13 22:14
gitworkflows.html	38.93 KB	-rw-r--r--	2025-07-22 14:32
gitworkflows.txt	17.01 KB	-rw-r--r--	2025-06-13 22:14
glossary-content.txt	31.84 KB	-rw-r--r--	2025-06-13 22:14
howto-index.html	22.45 KB	-rw-r--r--	2025-07-22 14:32
howto-index.txt	3.91 KB	-rw-r--r--	2025-07-22 14:30
i18n.txt	2.87 KB	-rw-r--r--	2025-06-13 22:14
line-range-format.txt	1.13 KB	-rw-r--r--	2025-06-13 22:14
line-range-options.txt	761 B	-rw-r--r--	2025-06-13 22:14
merge-options.txt	7.07 KB	-rw-r--r--	2025-06-13 22:14
merge-strategies.txt	6.46 KB	-rw-r--r--	2025-06-13 22:14
mergetools-diff.txt	1.47 KB	-rw-r--r--	2025-07-22 14:30
mergetools-merge.txt	2.53 KB	-rw-r--r--	2025-07-22 14:30
object-format-disclaimer.txt	470 B	-rw-r--r--	2025-06-13 22:14
pretty-formats.txt	15.3 KB	-rw-r--r--	2025-06-13 22:14
pretty-options.txt	4.1 KB	-rw-r--r--	2025-06-13 22:14
pull-fetch-param.txt	5.35 KB	-rw-r--r--	2025-06-13 22:14
ref-reachability-filters.txt	391 B	-rw-r--r--	2025-06-13 22:14
rerere-options.txt	414 B	-rw-r--r--	2025-06-13 22:14
rev-list-description.txt	2.47 KB	-rw-r--r--	2025-06-13 22:14
rev-list-options.txt	45.81 KB	-rw-r--r--	2025-06-13 22:14
revisions.txt	16.71 KB	-rw-r--r--	2025-06-13 22:14
scalar.html	25.44 KB	-rw-r--r--	2025-07-22 14:32
scalar.txt	5.91 KB	-rw-r--r--	2025-06-13 22:14
sequencer.txt	472 B	-rw-r--r--	2025-06-13 22:14
signoff-option.txt	781 B	-rw-r--r--	2025-06-13 22:14
trace2-target-values.txt	529 B	-rw-r--r--	2025-06-13 22:14
transfer-data-leaks.txt	1.67 KB	-rw-r--r--	2025-06-13 22:14
urls-remotes.txt	2.58 KB	-rw-r--r--	2025-06-13 22:14
urls.txt	3.55 KB	-rw-r--r--	2025-06-13 22:14
user-manual.html	269.27 KB	-rw-r--r--	2025-07-22 14:32
user-manual.txt	169.45 KB	-rw-r--r--	2025-06-13 22:14

Rename

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
    "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
<meta name="generator" content="AsciiDoc 8.6.10" />
<title>gitrevisions(7)</title>
<style type="text/css">
/* Shared CSS for AsciiDoc xhtml11 and html5 backends */

/* Default font. */
body {
  font-family: Georgia,serif;
}

/* Title font. */
h1, h2, h3, h4, h5, h6,
div.title, caption.title,
thead, p.table.header,
#toctitle,
#author, #revnumber, #revdate, #revremark,
#footer {
  font-family: Arial,Helvetica,sans-serif;
}

body {
  margin: 1em 5% 1em 5%;
}

a {
  color: blue;
  text-decoration: underline;
}
a:visited {
  color: fuchsia;
}

em {
  font-style: italic;
  color: navy;
}

strong {
  font-weight: bold;
  color: #083194;
}

h1, h2, h3, h4, h5, h6 {
  color: #527bbd;
  margin-top: 1.2em;
  margin-bottom: 0.5em;
  line-height: 1.3;
}

h1, h2, h3 {
  border-bottom: 2px solid silver;
}
h2 {
  padding-top: 0.5em;
}
h3 {
  float: left;
}
h3 + * {
  clear: left;
}
h5 {
  font-size: 1.0em;
}

div.sectionbody {
  margin-left: 0;
}

hr {
  border: 1px solid silver;
}

p {
  margin-top: 0.5em;
  margin-bottom: 0.5em;
}

ul, ol, li > p {
  margin-top: 0;
}
ul > li     { color: #aaa; }
ul > li > * { color: black; }

.monospaced, code, pre {
  font-family: "Courier New", Courier, monospace;
  font-size: inherit;
  color: navy;
  padding: 0;
  margin: 0;
}
pre {
  white-space: pre-wrap;
}

#author {
  color: #527bbd;
  font-weight: bold;
  font-size: 1.1em;
}
#email {
}
#revnumber, #revdate, #revremark {
}

#footer {
  font-size: small;
  border-top: 2px solid silver;
  padding-top: 0.5em;
  margin-top: 4.0em;
}
#footer-text {
  float: left;
  padding-bottom: 0.5em;
}
#footer-badges {
  float: right;
  padding-bottom: 0.5em;
}

#preamble {
  margin-top: 1.5em;
  margin-bottom: 1.5em;
}
div.imageblock, div.exampleblock, div.verseblock,
div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
div.admonitionblock {
  margin-top: 1.0em;
  margin-bottom: 1.5em;
}
div.admonitionblock {
  margin-top: 2.0em;
  margin-bottom: 2.0em;
  margin-right: 10%;
  color: #606060;
}

div.content { /* Block element content. */
  padding: 0;
}

/* Block element titles. */
div.title, caption.title {
  color: #527bbd;
  font-weight: bold;
  text-align: left;
  margin-top: 1.0em;
  margin-bottom: 0.5em;
}
div.title + * {
  margin-top: 0;
}

td div.title:first-child {
  margin-top: 0.0em;
}
div.content div.title:first-child {
  margin-top: 0.0em;
}
div.content + div.title {
  margin-top: 0.0em;
}

div.sidebarblock > div.content {
  background: #ffffee;
  border: 1px solid #dddddd;
  border-left: 4px solid #f0f0f0;
  padding: 0.5em;
}

div.listingblock > div.content {
  border: 1px solid #dddddd;
  border-left: 5px solid #f0f0f0;
  background: #f8f8f8;
  padding: 0.5em;
}

div.quoteblock, div.verseblock {
  padding-left: 1.0em;
  margin-left: 1.0em;
  margin-right: 10%;
  border-left: 5px solid #f0f0f0;
  color: #888;
}

div.quoteblock > div.attribution {
  padding-top: 0.5em;
  text-align: right;
}

div.verseblock > pre.content {
  font-family: inherit;
  font-size: inherit;
}
div.verseblock > div.attribution {
  padding-top: 0.75em;
  text-align: left;
}
/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
div.verseblock + div.attribution {
  text-align: left;
}

div.admonitionblock .icon {
  vertical-align: top;
  font-size: 1.1em;
  font-weight: bold;
  text-decoration: underline;
  color: #527bbd;
  padding-right: 0.5em;
}
div.admonitionblock td.content {
  padding-left: 0.5em;
  border-left: 3px solid #dddddd;
}

div.exampleblock > div.content {
  border-left: 3px solid #dddddd;
  padding-left: 0.5em;
}

div.imageblock div.content { padding-left: 0; }
span.image img { border-style: none; vertical-align: text-bottom; }
a.image:visited { color: white; }

dl {
  margin-top: 0.8em;
  margin-bottom: 0.8em;
}
dt {
  margin-top: 0.5em;
  margin-bottom: 0;
  font-style: normal;
  color: navy;
}
dd > *:first-child {
  margin-top: 0.1em;
}

ul, ol {
    list-style-position: outside;
}
ol.arabic {
  list-style-type: decimal;
}
ol.loweralpha {
  list-style-type: lower-alpha;
}
ol.upperalpha {
  list-style-type: upper-alpha;
}
ol.lowerroman {
  list-style-type: lower-roman;
}
ol.upperroman {
  list-style-type: upper-roman;
}

div.compact ul, div.compact ol,
div.compact p, div.compact p,
div.compact div, div.compact div {
  margin-top: 0.1em;
  margin-bottom: 0.1em;
}

tfoot {
  font-weight: bold;
}
td > div.verse {
  white-space: pre;
}

div.hdlist {
  margin-top: 0.8em;
  margin-bottom: 0.8em;
}
div.hdlist tr {
  padding-bottom: 15px;
}
dt.hdlist1.strong, td.hdlist1.strong {
  font-weight: bold;
}
td.hdlist1 {
  vertical-align: top;
  font-style: normal;
  padding-right: 0.8em;
  color: navy;
}
td.hdlist2 {
  vertical-align: top;
}
div.hdlist.compact tr {
  margin: 0;
  padding-bottom: 0;
}

.comment {
  background: yellow;
}

.footnote, .footnoteref {
  font-size: 0.8em;
}

span.footnote, span.footnoteref {
  vertical-align: super;
}

#footnotes {
  margin: 20px 0 20px 0;
  padding: 7px 0 0 0;
}

#footnotes div.footnote {
  margin: 0 0 5px 0;
}

#footnotes hr {
  border: none;
  border-top: 1px solid silver;
  height: 1px;
  text-align: left;
  margin-left: 0;
  width: 20%;
  min-width: 100px;
}

div.colist td {
  padding-right: 0.5em;
  padding-bottom: 0.3em;
  vertical-align: top;
}
div.colist td img {
  margin-top: 0.3em;
}

@media print {
  #footer-badges { display: none; }
}

#toc {
  margin-bottom: 2.5em;
}

#toctitle {
  color: #527bbd;
  font-size: 1.1em;
  font-weight: bold;
  margin-top: 1.0em;
  margin-bottom: 0.1em;
}

div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
  margin-top: 0;
  margin-bottom: 0;
}
div.toclevel2 {
  margin-left: 2em;
  font-size: 0.9em;
}
div.toclevel3 {
  margin-left: 4em;
  font-size: 0.9em;
}
div.toclevel4 {
  margin-left: 6em;
  font-size: 0.9em;
}

span.aqua { color: aqua; }
span.black { color: black; }
span.blue { color: blue; }
span.fuchsia { color: fuchsia; }
span.gray { color: gray; }
span.green { color: green; }
span.lime { color: lime; }
span.maroon { color: maroon; }
span.navy { color: navy; }
span.olive { color: olive; }
span.purple { color: purple; }
span.red { color: red; }
span.silver { color: silver; }
span.teal { color: teal; }
span.white { color: white; }
span.yellow { color: yellow; }

span.aqua-background { background: aqua; }
span.black-background { background: black; }
span.blue-background { background: blue; }
span.fuchsia-background { background: fuchsia; }
span.gray-background { background: gray; }
span.green-background { background: green; }
span.lime-background { background: lime; }
span.maroon-background { background: maroon; }
span.navy-background { background: navy; }
span.olive-background { background: olive; }
span.purple-background { background: purple; }
span.red-background { background: red; }
span.silver-background { background: silver; }
span.teal-background { background: teal; }
span.white-background { background: white; }
span.yellow-background { background: yellow; }

span.big { font-size: 2em; }
span.small { font-size: 0.6em; }

span.underline { text-decoration: underline; }
span.overline { text-decoration: overline; }
span.line-through { text-decoration: line-through; }

div.unbreakable { page-break-inside: avoid; }

/*
 * xhtml11 specific
 *
 * */

div.tableblock {
  margin-top: 1.0em;
  margin-bottom: 1.5em;
}
div.tableblock > table {
  border: 3px solid #527bbd;
}
thead, p.table.header {
  font-weight: bold;
  color: #527bbd;
}
p.table {
  margin-top: 0;
}
/* Because the table frame attribute is overriden by CSS in most browsers. */
div.tableblock > table[frame="void"] {
  border-style: none;
}
div.tableblock > table[frame="hsides"] {
  border-left-style: none;
  border-right-style: none;
}
div.tableblock > table[frame="vsides"] {
  border-top-style: none;
  border-bottom-style: none;
}

/*
 * html5 specific
 *
 * */

table.tableblock {
  margin-top: 1.0em;
  margin-bottom: 1.5em;
}
thead, p.tableblock.header {
  font-weight: bold;
  color: #527bbd;
}
p.tableblock {
  margin-top: 0;
}
table.tableblock {
  border-width: 3px;
  border-spacing: 0px;
  border-style: solid;
  border-color: #527bbd;
  border-collapse: collapse;
}
th.tableblock, td.tableblock {
  border-width: 1px;
  padding: 4px;
  border-style: solid;
  border-color: #527bbd;
}

table.tableblock.frame-topbot {
  border-left-style: hidden;
  border-right-style: hidden;
}
table.tableblock.frame-sides {
  border-top-style: hidden;
  border-bottom-style: hidden;
}
table.tableblock.frame-none {
  border-style: hidden;
}

th.tableblock.halign-left, td.tableblock.halign-left {
  text-align: left;
}
th.tableblock.halign-center, td.tableblock.halign-center {
  text-align: center;
}
th.tableblock.halign-right, td.tableblock.halign-right {
  text-align: right;
}

th.tableblock.valign-top, td.tableblock.valign-top {
  vertical-align: top;
}
th.tableblock.valign-middle, td.tableblock.valign-middle {
  vertical-align: middle;
}
th.tableblock.valign-bottom, td.tableblock.valign-bottom {
  vertical-align: bottom;
}

/*
 * manpage specific
 *
 * */

body.manpage h1 {
  padding-top: 0.5em;
  padding-bottom: 0.5em;
  border-top: 2px solid silver;
  border-bottom: 2px solid silver;
}
body.manpage h2 {
  border-style: none;
}
body.manpage div.sectionbody {
  margin-left: 3em;
}

@media print {
  body.manpage div#toc { display: none; }
}

</style>
<script type="text/javascript">
/*<![CDATA[*/
var asciidoc = {  // Namespace.

/////////////////////////////////////////////////////////////////////
// Table Of Contents generator
/////////////////////////////////////////////////////////////////////

/* Author: Mihai Bazon, September 2002
 * http://students.infoiasi.ro/~mishoo
 *
 * Table Of Content generator
 * Version: 0.4
 *
 * Feel free to use this script under the terms of the GNU General Public
 * License, as long as you do not remove or alter this notice.
 */

/* modified by Troy D. Hanson, September 2006. License: GPL */
 /* modified by Stuart Rackham, 2006, 2009. License: GPL */

// toclevels = 1..4.
toc: function (toclevels) {

function getText(el) {
    var text = "";
    for (var i = el.firstChild; i != null; i = i.nextSibling) {
      if (i.nodeType == 3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
        text += i.data;
      else if (i.firstChild != null)
        text += getText(i);
    }
    return text;
  }

function TocEntry(el, text, toclevel) {
    this.element = el;
    this.text = text;
    this.toclevel = toclevel;
  }

var toc = document.getElementById("toc");
  if (!toc) {
    return;
  }

// Delete existing TOC entries in case we're reloading the TOC.
  var tocEntriesToRemove = [];
  var i;
  for (i = 0; i < toc.childNodes.length; i++) {
    var entry = toc.childNodes[i];
    if (entry.nodeName.toLowerCase() == 'div'
     && entry.getAttribute("class")
     && entry.getAttribute("class").match(/^toclevel/))
      tocEntriesToRemove.push(entry);
  }
  for (i = 0; i < tocEntriesToRemove.length; i++) {
    toc.removeChild(tocEntriesToRemove[i]);
  }

// Rebuild TOC entries.
  var entries = tocEntries(document.getElementById("content"), toclevels);
  for (var i = 0; i < entries.length; ++i) {
    var entry = entries[i];
    if (entry.element.id == "")
      entry.element.id = "_toc_" + i;
    var a = document.createElement("a");
    a.href = "#" + entry.element.id;
    a.appendChild(document.createTextNode(entry.text));
    var div = document.createElement("div");
    div.appendChild(a);
    div.className = "toclevel" + entry.toclevel;
    toc.appendChild(div);
  }
  if (entries.length == 0)
    toc.parentNode.removeChild(toc);
},

/////////////////////////////////////////////////////////////////////
// Footnotes generator
/////////////////////////////////////////////////////////////////////

/* Based on footnote generation code from:
 * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
 */

footnotes: function () {
  // Delete existing footnote entries in case we're reloading the footnodes.
  var i;
  var noteholder = document.getElementById("footnotes");
  if (!noteholder) {
    return;
  }
  var entriesToRemove = [];
  for (i = 0; i < noteholder.childNodes.length; i++) {
    var entry = noteholder.childNodes[i];
    if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
      entriesToRemove.push(entry);
  }
  for (i = 0; i < entriesToRemove.length; i++) {
    noteholder.removeChild(entriesToRemove[i]);
  }

// Rebuild footnote entries.
  var cont = document.getElementById("content");
  var spans = cont.getElementsByTagName("span");
  var refs = {};
  var n = 0;
  for (i=0; i<spans.length; i++) {
    if (spans[i].className == "footnote") {
      n++;
      var note = spans[i].getAttribute("data-note");
      if (!note) {
        // Use [\s\S] in place of . so multi-line matches work.
        // Because JavaScript has no s (dotall) regex flag.
        note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
        spans[i].innerHTML =
          "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
          "' title='View footnote' class='footnote'>" + n + "</a>]";
        spans[i].setAttribute("data-note", note);
      }
      noteholder.innerHTML +=
        "<div class='footnote' id='_footnote_" + n + "'>" +
        "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
        n + "</a>. " + note + "</div>";
      var id =spans[i].getAttribute("id");
      if (id != null) refs["#"+id] = n;
    }
  }
  if (n == 0)
    noteholder.parentNode.removeChild(noteholder);
  else {
    // Process footnoterefs.
    for (i=0; i<spans.length; i++) {
      if (spans[i].className == "footnoteref") {
        var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
        href = href.match(/#.*/)[0];  // Because IE return full URL.
        n = refs[href];
        spans[i].innerHTML =
          "[<a href='#_footnote_" + n +
          "' title='View footnote' class='footnote'>" + n + "</a>]";
      }
    }
  }
},

install: function(toclevels) {
  var timerId;

function reinstall() {
    asciidoc.footnotes();
    if (toclevels) {
      asciidoc.toc(toclevels);
    }
  }

function reinstallAndRemoveTimer() {
    clearInterval(timerId);
    reinstall();
  }

timerId = setInterval(reinstall, 500);
  if (document.addEventListener)
    document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
  else
    window.onload = reinstallAndRemoveTimer;
}

}
asciidoc.install();
/*]]>*/
</script>
</head>
<body class="manpage">
<div id="header">
<h1>
gitrevisions(7) Manual Page
</h1>
<h2>NAME</h2>
<div class="sectionbody">
<p>gitrevisions -
   Specifying revisions and ranges for Git
</p>
</div>
</div>
<div id="content">
<div class="sect1">
<h2 id="_synopsis">SYNOPSIS</h2>
<div class="sectionbody">
<div class="paragraph"><p>gitrevisions</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_description">DESCRIPTION</h2>
<div class="sectionbody">
<div class="paragraph"><p>Many Git commands take revision parameters as arguments. Depending on
the command, they denote a specific commit or, for commands which
walk the revision graph (such as <a href="git-log.html">git-log(1)</a>), all commits which are
reachable from that commit. For commands that walk the revision graph one can
also specify a range of revisions explicitly.</p></div>
<div class="paragraph"><p>In addition, some Git commands (such as <a href="git-show.html">git-show(1)</a> and
<a href="git-push.html">git-push(1)</a>) can also take revision parameters which denote
other objects than commits, e.g. blobs ("files") or trees
("directories of files").</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_specifying_revisions">SPECIFYING REVISIONS</h2>
<div class="sectionbody">
<div class="paragraph"><p>A revision parameter <em>&lt;rev&gt;</em> typically, but not necessarily, names a
commit object.  It uses what is called an <em>extended SHA-1</em>
syntax.  Here are various ways to spell object names.  The
ones listed near the end of this list name trees and
blobs contained in a commit.</p></div>
<div class="admonitionblock">
<table><tr>
<td class="icon">
<div class="title">Note</div>
</td>
<td class="content">This document shows the "raw" syntax as seen by git. The shell
and other UIs might require additional quoting to protect special
characters and to avoid word splitting.</td>
</tr></table>
</div>
<div class="dlist"><dl>
<dt class="hdlist1">
<em>&lt;sha1&gt;</em>, e.g. <em>dae86e1950b1277e545cee180551750029cfe735</em>, <em>dae86e</em>
</dt>
<dd>
<p>
  The full SHA-1 object name (40-byte hexadecimal string), or
  a leading substring that is unique within the repository.
  E.g. dae86e1950b1277e545cee180551750029cfe735 and dae86e both
  name the same commit object if there is no other object in
  your repository whose object name starts with dae86e.
</p>
</dd>
<dt class="hdlist1">
<em>&lt;describeOutput&gt;</em>, e.g. <em>v1.7.4.2-679-g3bee7fb</em>
</dt>
<dd>
<p>
  Output from <code>git describe</code>; i.e. a closest tag, optionally
  followed by a dash and a number of commits, followed by a dash, a
  <em>g</em>, and an abbreviated object name.
</p>
</dd>
<dt class="hdlist1">
<em>&lt;refname&gt;</em>, e.g. <em>master</em>, <em>heads/master</em>, <em>refs/heads/master</em>
</dt>
<dd>
<p>
  A symbolic ref name.  E.g. <em>master</em> typically means the commit
  object referenced by <em>refs/heads/master</em>.  If you
  happen to have both <em>heads/master</em> and <em>tags/master</em>, you can
  explicitly say <em>heads/master</em> to tell Git which one you mean.
  When ambiguous, a <em>&lt;refname&gt;</em> is disambiguated by taking the
  first match in the following rules:
</p>
<div class="olist arabic"><ol class="arabic">
<li>
<p>
If <em>$GIT_DIR/&lt;refname&gt;</em> exists, that is what you mean (this is usually
    useful only for <code>HEAD</code>, <code>FETCH_HEAD</code>, <code>ORIG_HEAD</code>, <code>MERGE_HEAD</code>,
    <code>REBASE_HEAD</code>, <code>REVERT_HEAD</code>, <code>CHERRY_PICK_HEAD</code>, <code>BISECT_HEAD</code>
    and <code>AUTO_MERGE</code>);
</p>
</li>
<li>
<p>
otherwise, <em>refs/&lt;refname&gt;</em> if it exists;
</p>
</li>
<li>
<p>
otherwise, <em>refs/tags/&lt;refname&gt;</em> if it exists;
</p>
</li>
<li>
<p>
otherwise, <em>refs/heads/&lt;refname&gt;</em> if it exists;
</p>
</li>
<li>
<p>
otherwise, <em>refs/remotes/&lt;refname&gt;</em> if it exists;
</p>
</li>
<li>
<p>
otherwise, <em>refs/remotes/&lt;refname&gt;/HEAD</em> if it exists.
</p>
</li>
</ol></div>
<div class="dlist"><dl>
<dt class="hdlist1">
<code>HEAD</code>
</dt>
<dd>
<p>
    names the commit on which you based the changes in the working tree.
</p>
</dd>
<dt class="hdlist1">
<code>FETCH_HEAD</code>
</dt>
<dd>
<p>
    records the branch which you fetched from a remote repository with
    your last <code>git fetch</code> invocation.
</p>
</dd>
<dt class="hdlist1">
<code>ORIG_HEAD</code>
</dt>
<dd>
<p>
    is created by commands that move your <code>HEAD</code> in a drastic way (<code>git
    am</code>, <code>git merge</code>, <code>git rebase</code>, <code>git reset</code>), to record the position
    of the <code>HEAD</code> before their operation, so that you can easily change
    the tip of the branch back to the state before you ran them.
</p>
</dd>
<dt class="hdlist1">
<code>MERGE_HEAD</code>
</dt>
<dd>
<p>
    records the commit(s) which you are merging into your branch when you
    run <code>git merge</code>.
</p>
</dd>
<dt class="hdlist1">
<code>REBASE_HEAD</code>
</dt>
<dd>
<p>
    during a rebase, records the commit at which the operation is
    currently stopped, either because of conflicts or an <code>edit</code> command in
    an interactive rebase.
</p>
</dd>
<dt class="hdlist1">
<code>REVERT_HEAD</code>
</dt>
<dd>
<p>
    records the commit which you are reverting when you run <code>git revert</code>.
</p>
</dd>
<dt class="hdlist1">
<code>CHERRY_PICK_HEAD</code>
</dt>
<dd>
<p>
    records the commit which you are cherry-picking when you run <code>git
    cherry-pick</code>.
</p>
</dd>
<dt class="hdlist1">
<code>BISECT_HEAD</code>
</dt>
<dd>
<p>
    records the current commit to be tested when you run <code>git bisect
    --no-checkout</code>.
</p>
</dd>
<dt class="hdlist1">
<code>AUTO_MERGE</code>
</dt>
<dd>
<p>
    records a tree object corresponding to the state the
    <em>ort</em> merge strategy wrote to the working tree when a merge operation
    resulted in conflicts.
</p>
</dd>
</dl></div>
<div class="paragraph"><p>Note that any of the <em>refs/*</em> cases above may come either from
the <code>$GIT_DIR/refs</code> directory or from the <code>$GIT_DIR/packed-refs</code> file.
While the ref name encoding is unspecified, UTF-8 is preferred as
some output processing may assume ref names in UTF-8.</p></div>
</dd>
<dt class="hdlist1">
<em>@</em>
</dt>
<dd>
<p>
  <em>@</em> alone is a shortcut for <code>HEAD</code>.
</p>
</dd>
<dt class="hdlist1">
<em>[&lt;refname&gt;]@{&lt;date&gt;}</em>, e.g. <em>master@{yesterday}</em>, <em>HEAD@{5 minutes ago}</em>
</dt>
<dd>
<p>
  A ref followed by the suffix <em>@</em> with a date specification
  enclosed in a brace
  pair (e.g. <em>{yesterday}</em>, <em>{1 month 2 weeks 3 days 1 hour 1
  second ago}</em> or <em>{1979-02-26 18:30:00}</em>) specifies the value
  of the ref at a prior point in time.  This suffix may only be
  used immediately following a ref name and the ref must have an
  existing log (<em>$GIT_DIR/logs/&lt;ref&gt;</em>). Note that this looks up the state
  of your <strong>local</strong> ref at a given time; e.g., what was in your local
  <em>master</em> branch last week. If you want to look at commits made during
  certain times, see <code>--since</code> and <code>--until</code>.
</p>
</dd>
<dt class="hdlist1">
<em>&lt;refname&gt;@{&lt;n&gt;}</em>, e.g. <em>master@{1}</em>
</dt>
<dd>
<p>
  A ref followed by the suffix <em>@</em> with an ordinal specification
  enclosed in a brace pair (e.g. <em>{1}</em>, <em>{15}</em>) specifies
  the n-th prior value of that ref.  For example <em>master@{1}</em>
  is the immediate prior value of <em>master</em> while <em>master@{5}</em>
  is the 5th prior value of <em>master</em>. This suffix may only be used
  immediately following a ref name and the ref must have an existing
  log (<em>$GIT_DIR/logs/&lt;refname&gt;</em>).
</p>
</dd>
<dt class="hdlist1">
<em>@{&lt;n&gt;}</em>, e.g. <em>@{1}</em>
</dt>
<dd>
<p>
  You can use the <em>@</em> construct with an empty ref part to get at a
  reflog entry of the current branch. For example, if you are on
  branch <em>blabla</em> then <em>@{1}</em> means the same as <em>blabla@{1}</em>.
</p>
</dd>
<dt class="hdlist1">
<em>@{-&lt;n&gt;}</em>, e.g. <em>@{-1}</em>
</dt>
<dd>
<p>
  The construct <em>@{-&lt;n&gt;}</em> means the &lt;n&gt;th branch/commit checked out
  before the current one.
</p>
</dd>
<dt class="hdlist1">
<em>[&lt;branchname&gt;]@{upstream}</em>, e.g. <em>master@{upstream}</em>, <em>@{u}</em>
</dt>
<dd>
<p>
  A branch B may be set up to build on top of a branch X (configured with
  <code>branch.&lt;name&gt;.merge</code>) at a remote R (configured with
  the branch X taken from remote R, typically found at <code>refs/remotes/R/X</code>.
</p>
</dd>
<dt class="hdlist1">
<em>[&lt;branchname&gt;]@{push}</em>, e.g. <em>master@{push}</em>, <em>@{push}</em>
</dt>
<dd>
<p>
  The suffix <em>@{push}</em> reports the branch "where we would push to" if
  <code>git push</code> were run while <code>branchname</code> was checked out (or the current
  <code>HEAD</code> if no branchname is specified). Like for <em>@{upstream}</em>, we report
  the remote-tracking branch that corresponds to that branch at the remote.
</p>
<div class="paragraph"><p>Here&#8217;s an example to make it more clear:</p></div>
<div class="listingblock">
<div class="content">
<pre><code>$ git config push.default current
$ git config remote.pushdefault myfork
$ git switch -c mybranch origin/master

$ git rev-parse --symbolic-full-name @{upstream}
refs/remotes/origin/master

$ git rev-parse --symbolic-full-name @{push}
refs/remotes/myfork/mybranch</code></pre>
</div></div>
<div class="paragraph"><p>Note in the example that we set up a triangular workflow, where we pull
from one location and push to another. In a non-triangular workflow,
<em>@{push}</em> is the same as <em>@{upstream}</em>, and there is no need for it.</p></div>
<div class="paragraph"><p>This suffix is also accepted when spelled in uppercase, and means the same
thing no matter the case.</p></div>
</dd>
<dt class="hdlist1">
<em>&lt;rev&gt;&#94;[&lt;n&gt;]</em>, e.g. <em>HEAD&#94;, v1.5.1&#94;0</em>
</dt>
<dd>
<p>
  A suffix <em>&#94;</em> to a revision parameter means the first parent of
  that commit object.  <em>&#94;&lt;n&gt;</em> means the &lt;n&gt;th parent (i.e.
  <em>&lt;rev&gt;&#94;</em>
  is equivalent to <em>&lt;rev&gt;&#94;1</em>).  As a special rule,
  <em>&lt;rev&gt;&#94;0</em> means the commit itself and is used when <em>&lt;rev&gt;</em> is the
  object name of a tag object that refers to a commit object.
</p>
</dd>
<dt class="hdlist1">
<em>&lt;rev&gt;&#126;[&lt;n&gt;]</em>, e.g. <em>HEAD&#126;, master&#126;3</em>
</dt>
<dd>
<p>
  A suffix <em>&#126;</em> to a revision parameter means the first parent of
  that commit object.
  A suffix <em>&#126;&lt;n&gt;</em> to a revision parameter means the commit
  object that is the &lt;n&gt;th generation ancestor of the named
  commit object, following only the first parents.  I.e. <em>&lt;rev&gt;&#126;3</em> is
  equivalent to <em>&lt;rev&gt;&#94;&#94;&#94;</em> which is equivalent to
  <em>&lt;rev&gt;&#94;1&#94;1&#94;1</em>.  See below for an illustration of
  the usage of this form.
</p>
</dd>
<dt class="hdlist1">
<em>&lt;rev&gt;&#94;{&lt;type&gt;}</em>, e.g. <em>v0.99.8&#94;{commit}</em>
</dt>
<dd>
<p>
  A suffix <em>&#94;</em> followed by an object type name enclosed in
  brace pair means dereference the object at <em>&lt;rev&gt;</em> recursively until
  an object of type <em>&lt;type&gt;</em> is found or the object cannot be
  dereferenced anymore (in which case, barf).
  For example, if <em>&lt;rev&gt;</em> is a commit-ish, <em>&lt;rev&gt;&#94;{commit}</em>
  describes the corresponding commit object.
  Similarly, if <em>&lt;rev&gt;</em> is a tree-ish, <em>&lt;rev&gt;&#94;{tree}</em>
  describes the corresponding tree object.
  <em>&lt;rev&gt;&#94;0</em>
  is a short-hand for <em>&lt;rev&gt;&#94;{commit}</em>.
</p>
<div class="paragraph"><p><em>&lt;rev&gt;&#94;{object}</em> can be used to make sure <em>&lt;rev&gt;</em> names an
object that exists, without requiring <em>&lt;rev&gt;</em> to be a tag, and
without dereferencing <em>&lt;rev&gt;</em>; because a tag is already an object,
it does not have to be dereferenced even once to get to an object.</p></div>
<div class="paragraph"><p><em>&lt;rev&gt;&#94;{tag}</em> can be used to ensure that <em>&lt;rev&gt;</em> identifies an
existing tag object.</p></div>
</dd>
<dt class="hdlist1">
<em>&lt;rev&gt;&#94;{}</em>, e.g. <em>v0.99.8&#94;{}</em>
</dt>
<dd>
<p>
  A suffix <em>&#94;</em> followed by an empty brace pair
  means the object could be a tag,
  and dereference the tag recursively until a non-tag object is
  found.
</p>
</dd>
<dt class="hdlist1">
<em>&lt;rev&gt;&#94;{/&lt;text&gt;}</em>, e.g. <em>HEAD^{/fix nasty bug}</em>
</dt>
<dd>
<p>
  A suffix <em>&#94;</em> to a revision parameter, followed by a brace
  pair that contains a text led by a slash,
  is the same as the <em>:/fix nasty bug</em> syntax below except that
  it returns the youngest matching commit which is reachable from
  the <em>&lt;rev&gt;</em> before <em>&#94;</em>.
</p>
</dd>
<dt class="hdlist1">
<em>:/&lt;text&gt;</em>, e.g. <em>:/fix nasty bug</em>
</dt>
<dd>
<p>
  A colon, followed by a slash, followed by a text, names
  a commit whose commit message matches the specified regular expression.
  This name returns the youngest matching commit which is
  reachable from any ref, including HEAD.
  The regular expression can match any part of the
  commit message. To match messages starting with a string, one can use
  e.g. <em>:/^foo</em>. The special sequence <em>:/!</em> is reserved for modifiers to what
  is matched. <em>:/!-foo</em> performs a negative match, while <em>:/!!foo</em> matches a
  literal <em>!</em> character, followed by <em>foo</em>. Any other sequence beginning with
  <em>:/!</em> is reserved for now.
  Depending on the given text, the shell&#8217;s word splitting rules might
  require additional quoting.
</p>
</dd>
<dt class="hdlist1">
<em>&lt;rev&gt;:&lt;path&gt;</em>, e.g. <em>HEAD:README</em>, <em>master:./README</em>
</dt>
<dd>
<p>
  A suffix <em>:</em> followed by a path names the blob or tree
  at the given path in the tree-ish object named by the part
  before the colon.
  A path starting with <em>./</em> or <em>../</em> is relative to the current working directory.
  The given path will be converted to be relative to the working tree&#8217;s root directory.
  This is most useful to address a blob or tree from a commit or tree that has
  the same tree structure as the working tree.
</p>
</dd>
<dt class="hdlist1">
<em>:[&lt;n&gt;:]&lt;path&gt;</em>, e.g. <em>:0:README</em>, <em>:README</em>
</dt>
<dd>
<p>
  A colon, optionally followed by a stage number (0 to 3) and a
  colon, followed by a path, names a blob object in the
  index at the given path. A missing stage number (and the colon
  that follows it) names a stage 0 entry. During a merge, stage
  1 is the common ancestor, stage 2 is the target branch&#8217;s version
  (typically the current branch), and stage 3 is the version from
  the branch which is being merged.
</p>
</dd>
</dl></div>
<div class="paragraph"><p>Here is an illustration, by Jon Loeliger.  Both commit nodes B
and C are parents of commit node A.  Parent commits are ordered
left-to-right.</p></div>
<div class="literalblock">
<div class="content">
<pre><code>G   H   I   J
 \ /     \ /
  D   E   F
   \  |  / \
    \ | /   |
     \|/    |
      B     C
       \   /
        \ /
         A</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>A =      = A^0
B = A^   = A^1     = A~1
C =      = A^2
D = A^^  = A^1^1   = A~2
E = B^2  = A^^2
F = B^3  = A^^3
G = A^^^ = A^1^1^1 = A~3
H = D^2  = B^^2    = A^^^2  = A~2^2
I = F^   = B^3^    = A^^3^
J = F^2  = B^3^2   = A^^3^2</code></pre>
</div></div>
</div>
</div>
<div class="sect1">
<h2 id="_specifying_ranges">SPECIFYING RANGES</h2>
<div class="sectionbody">
<div class="paragraph"><p>History traversing commands such as <code>git log</code> operate on a set
of commits, not just a single commit.</p></div>
<div class="paragraph"><p>For these commands,
specifying a single revision, using the notation described in the
previous section, means the set of commits <code>reachable</code> from the given
commit.</p></div>
<div class="paragraph"><p>Specifying several revisions means the set of commits reachable from
any of the given commits.</p></div>
<div class="paragraph"><p>A commit&#8217;s reachable set is the commit itself and the commits in
its ancestry chain.</p></div>
<div class="paragraph"><p>There are several notations to specify a set of connected commits
(called a "revision range"), illustrated below.</p></div>
<div class="sect2">
<h3 id="_commit_exclusions">Commit Exclusions</h3>
<div class="dlist"><dl>
<dt class="hdlist1">
<em>&#94;&lt;rev&gt;</em> (caret) Notation
</dt>
<dd>
<p>
 To exclude commits reachable from a commit, a prefix <em>&#94;</em>
 notation is used.  E.g. <em>&#94;r1 r2</em> means commits reachable
 from <em>r2</em> but exclude the ones reachable from <em>r1</em> (i.e. <em>r1</em> and
 its ancestors).
</p>
</dd>
</dl></div>
</div>
<div class="sect2">
<h3 id="_dotted_range_notations">Dotted Range Notations</h3>
<div class="dlist"><dl>
<dt class="hdlist1">
The <em>..</em> (two-dot) Range Notation
</dt>
<dd>
<p>
 The <em>&#94;r1 r2</em> set operation appears so often that there is a shorthand
 for it.  When you have two commits <em>r1</em> and <em>r2</em> (named according
 to the syntax explained in SPECIFYING REVISIONS above), you can ask
 for commits that are reachable from r2 excluding those that are reachable
 from r1 by <em>&#94;r1 r2</em> and it can be written as <em>r1..r2</em>.
</p>
</dd>
<dt class="hdlist1">
The <em>...</em> (three-dot) Symmetric Difference Notation
</dt>
<dd>
<p>
 A similar notation <em>r1...r2</em> is called symmetric difference
 of <em>r1</em> and <em>r2</em> and is defined as
 <em>r1 r2 --not $(git merge-base --all r1 r2)</em>.
 It is the set of commits that are reachable from either one of
 <em>r1</em> (left side) or <em>r2</em> (right side) but not from both.
</p>
</dd>
</dl></div>
<div class="paragraph"><p>In these two shorthand notations, you can omit one end and let it default to HEAD.
For example, <em>origin..</em> is a shorthand for <em>origin..HEAD</em> and asks "What
did I do since I forked from the origin branch?"  Similarly, <em>..origin</em>
is a shorthand for <em>HEAD..origin</em> and asks "What did the origin do since
I forked from them?"  Note that <em>..</em> would mean <em>HEAD..HEAD</em> which is an
empty range that is both reachable and unreachable from HEAD.</p></div>
<div class="paragraph"><p>Commands that are specifically designed to take two distinct ranges
(e.g. "git range-diff R1 R2" to compare two ranges) do exist, but
they are exceptions.  Unless otherwise noted, all "git" commands
that operate on a set of commits work on a single revision range.
In other words, writing two "two-dot range notation" next to each
other, e.g.</p></div>
<div class="literalblock">
<div class="content">
<pre><code>$ git log A..B C..D</code></pre>
</div></div>
<div class="paragraph"><p>does <strong>not</strong> specify two revision ranges for most commands.  Instead
it will name a single connected set of commits, i.e. those that are
reachable from either B or D but are reachable from neither A or C.
In a linear history like this:</p></div>
<div class="literalblock">
<div class="content">
<pre><code>---A---B---o---o---C---D</code></pre>
</div></div>
<div class="paragraph"><p>because A and B are reachable from C, the revision range specified
by these two dotted ranges is a single commit D.</p></div>
</div>
<div class="sect2">
<h3 id="_other_lt_rev_gt_94_parent_shorthand_notations">Other &lt;rev&gt;&#94; Parent Shorthand Notations</h3>
<div class="paragraph"><p>Three other shorthands exist, particularly useful for merge commits,
for naming a set that is formed by a commit and its parent commits.</p></div>
<div class="paragraph"><p>The <em>r1&#94;@</em> notation means all parents of <em>r1</em>.</p></div>
<div class="paragraph"><p>The <em>r1&#94;!</em> notation includes commit <em>r1</em> but excludes all of its parents.
By itself, this notation denotes the single commit <em>r1</em>.</p></div>
<div class="paragraph"><p>The <em>&lt;rev&gt;&#94;-[&lt;n&gt;]</em> notation includes <em>&lt;rev&gt;</em> but excludes the &lt;n&gt;th
parent (i.e. a shorthand for <em>&lt;rev&gt;&#94;&lt;n&gt;..&lt;rev&gt;</em>), with <em>&lt;n&gt;</em> = 1 if
not given. This is typically useful for merge commits where you
can just pass <em>&lt;commit&gt;&#94;-</em> to get all the commits in the branch
that was merged in merge commit <em>&lt;commit&gt;</em> (including <em>&lt;commit&gt;</em>
itself).</p></div>
<div class="paragraph"><p>While <em>&lt;rev&gt;&#94;&lt;n&gt;</em> was about specifying a single commit parent, these
three notations also consider its parents. For example you can say
<em>HEAD&#94;2&#94;@</em>, however you cannot say <em>HEAD&#94;@&#94;2</em>.</p></div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_revision_range_summary">Revision Range Summary</h2>
<div class="sectionbody">
<div class="dlist"><dl>
<dt class="hdlist1">
<em>&lt;rev&gt;</em>
</dt>
<dd>
<p>
        Include commits that are reachable from &lt;rev&gt; (i.e. &lt;rev&gt; and its
        ancestors).
</p>
</dd>
<dt class="hdlist1">
<em>&#94;&lt;rev&gt;</em>
</dt>
<dd>
<p>
        Exclude commits that are reachable from &lt;rev&gt; (i.e. &lt;rev&gt; and its
        ancestors).
</p>
</dd>
<dt class="hdlist1">
<em>&lt;rev1&gt;..&lt;rev2&gt;</em>
</dt>
<dd>
<p>
        Include commits that are reachable from &lt;rev2&gt; but exclude
        those that are reachable from &lt;rev1&gt;.  When either &lt;rev1&gt; or
        &lt;rev2&gt; is omitted, it defaults to <code>HEAD</code>.
</p>
</dd>
<dt class="hdlist1">
<em>&lt;rev1&gt;...&lt;rev2&gt;</em>
</dt>
<dd>
<p>
        Include commits that are reachable from either &lt;rev1&gt; or
        &lt;rev2&gt; but exclude those that are reachable from both.  When
        either &lt;rev1&gt; or &lt;rev2&gt; is omitted, it defaults to <code>HEAD</code>.
</p>
</dd>
<dt class="hdlist1">
<em>&lt;rev&gt;&#94;@</em>, e.g. <em>HEAD&#94;@</em>
</dt>
<dd>
<p>
  A suffix <em>&#94;</em> followed by an at sign is the same as listing
  all parents of <em>&lt;rev&gt;</em> (meaning, include anything reachable from
  its parents, but not the commit itself).
</p>
</dd>
<dt class="hdlist1">
<em>&lt;rev&gt;&#94;!</em>, e.g. <em>HEAD&#94;!</em>
</dt>
<dd>
<p>
  A suffix <em>&#94;</em> followed by an exclamation mark is the same
  as giving commit <em>&lt;rev&gt;</em> and all its parents prefixed with
  <em>&#94;</em> to exclude them (and their ancestors).
</p>
</dd>
<dt class="hdlist1">
<em>&lt;rev&gt;&#94;-&lt;n&gt;</em>, e.g. <em>HEAD&#94;-, HEAD&#94;-2</em>
</dt>
<dd>
<p>
        Equivalent to <em>&lt;rev&gt;&#94;&lt;n&gt;..&lt;rev&gt;</em>, with <em>&lt;n&gt;</em> = 1 if not
        given.
</p>
</dd>
</dl></div>
<div class="paragraph"><p>Here are a handful of examples using the Loeliger illustration above,
with each step in the notation&#8217;s expansion and selection carefully
spelt out:</p></div>
<div class="literalblock">
<div class="content">
<pre><code>   Args   Expanded arguments    Selected commits
   D                            G H D
   D F                          G H I J D F
   ^G D                         H D
   ^D B                         E I J F B
   ^D B C                       E I J F B C
   C                            I J F C
   B..C   = ^B C                C
   B...C  = B ^F C              G H D E B C
   B^-    = B^..B
          = ^B^1 B              E I J F B
   C^@    = C^1
          = F                   I J F
   B^@    = B^1 B^2 B^3
          = D E F               D G H E F I J
   C^!    = C ^C^@
          = C ^C^1
          = C ^F                C
   B^!    = B ^B^@
          = B ^B^1 ^B^2 ^B^3
          = B ^D ^E ^F          B
   F^! D  = F ^I ^J D           G H D F</code></pre>
</div></div>
</div>
</div>
<div class="sect1">
<h2 id="_see_also">SEE ALSO</h2>
<div class="sectionbody">
<div class="paragraph"><p><a href="git-rev-parse.html">git-rev-parse(1)</a></p></div>
</div>
</div>
<div class="sect1">
<h2 id="_git">GIT</h2>
<div class="sectionbody">
<div class="paragraph"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
</div>
</div>
</div>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
Last updated
 2025-06-13 22:14:31 UTC
</div>
</div>
</body>
</html>