Linux ip-148-66-134-25.ip.secureserver.net 3.10.0-1160.119.1.el7.tuxcare.els10.x86_64 #1 SMP Fri Oct 11 21:40:41 UTC 2024 x86_64
Apache
: 148.66.134.25 | : 3.137.169.14
66 Domain
8.0.30
amvm
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
BLACK DEFEND!
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
git-1.8.3.1 /
[ HOME SHELL ]
Name
Size
Permission
Action
RelNotes
[ DIR ]
drwxr-xr-x
contrib
[ DIR ]
drwxr-xr-x
howto
[ DIR ]
drwxr-xr-x
technical
[ DIR ]
drwxr-xr-x
COPYING
18.33
KB
-rw-r--r--
README
2.56
KB
-rw-r--r--
blame-options.txt
3.95
KB
-rw-r--r--
cmds-ancillaryinterrogators.tx...
1.18
KB
-rw-r--r--
cmds-ancillarymanipulators.txt
1005
B
-rw-r--r--
cmds-foreignscminterface.txt
760
B
-rw-r--r--
cmds-mainporcelain.txt
2.5
KB
-rw-r--r--
cmds-plumbinginterrogators.txt
1.34
KB
-rw-r--r--
cmds-plumbingmanipulators.txt
1.21
KB
-rw-r--r--
cmds-purehelpers.txt
1.11
KB
-rw-r--r--
cmds-synchelpers.txt
543
B
-rw-r--r--
cmds-synchingrepositories.txt
397
B
-rw-r--r--
config.txt
90.14
KB
-rw-r--r--
date-formats.txt
848
B
-rw-r--r--
diff-config.txt
6.87
KB
-rw-r--r--
diff-format.txt
5.44
KB
-rw-r--r--
diff-generate-patch.txt
6.44
KB
-rw-r--r--
diff-options.txt
18.12
KB
-rw-r--r--
docbook-xsl.css
4.45
KB
-rw-r--r--
everyday.html
35.06
KB
-rw-r--r--
everyday.txt
12.71
KB
-rw-r--r--
fetch-options.txt
4.22
KB
-rw-r--r--
git-add.html
35.63
KB
-rw-r--r--
git-add.txt
13.96
KB
-rw-r--r--
git-am.html
25.86
KB
-rw-r--r--
git-am.txt
6.02
KB
-rw-r--r--
git-annotate.html
23.32
KB
-rw-r--r--
git-annotate.txt
752
B
-rw-r--r--
git-apply.html
30.82
KB
-rw-r--r--
git-apply.txt
10.07
KB
-rw-r--r--
git-archive.html
25.88
KB
-rw-r--r--
git-archive.txt
6.05
KB
-rw-r--r--
git-bisect-lk2009.html
78.86
KB
-rw-r--r--
git-bisect-lk2009.txt
48.08
KB
-rw-r--r--
git-bisect.html
33.08
KB
-rw-r--r--
git-bisect.txt
12.38
KB
-rw-r--r--
git-blame.html
37.08
KB
-rw-r--r--
git-blame.txt
7.63
KB
-rw-r--r--
git-branch.html
31.29
KB
-rw-r--r--
git-branch.txt
9.87
KB
-rw-r--r--
git-bundle.html
25.72
KB
-rw-r--r--
git-bundle.txt
6.89
KB
-rw-r--r--
git-cat-file.html
21.04
KB
-rw-r--r--
git-cat-file.txt
2.9
KB
-rw-r--r--
git-check-attr.html
21.17
KB
-rw-r--r--
git-check-attr.txt
2.72
KB
-rw-r--r--
git-check-ignore.html
20.25
KB
-rw-r--r--
git-check-ignore.txt
2.35
KB
-rw-r--r--
git-check-ref-format.html
22.43
KB
-rw-r--r--
git-check-ref-format.txt
4.08
KB
-rw-r--r--
git-checkout-index.html
24.34
KB
-rw-r--r--
git-checkout-index.txt
5.31
KB
-rw-r--r--
git-checkout.html
38.47
KB
-rw-r--r--
git-checkout.txt
15.61
KB
-rw-r--r--
git-cherry-pick.html
28.28
KB
-rw-r--r--
git-cherry-pick.txt
7.73
KB
-rw-r--r--
git-cherry.html
19.15
KB
-rw-r--r--
git-cherry.txt
1.71
KB
-rw-r--r--
git-citool.html
17.13
KB
-rw-r--r--
git-citool.txt
543
B
-rw-r--r--
git-clean.html
19.45
KB
-rw-r--r--
git-clean.txt
1.92
KB
-rw-r--r--
git-clone.html
34.75
KB
-rw-r--r--
git-clone.txt
9.84
KB
-rw-r--r--
git-column.html
18.47
KB
-rw-r--r--
git-column.txt
1.14
KB
-rw-r--r--
git-commit-tree.html
25.04
KB
-rw-r--r--
git-commit-tree.txt
2.79
KB
-rw-r--r--
git-commit.html
43.18
KB
-rw-r--r--
git-commit.txt
14.96
KB
-rw-r--r--
git-config.html
181.42
KB
-rw-r--r--
git-config.txt
11.52
KB
-rw-r--r--
git-count-objects.html
18.11
KB
-rw-r--r--
git-count-objects.txt
1.06
KB
-rw-r--r--
git-credential-cache--daemon.h...
17.4
KB
-rw-r--r--
git-credential-cache--daemon.t...
684
B
-rw-r--r--
git-credential-cache.html
19.26
KB
-rw-r--r--
git-credential-cache.txt
2.13
KB
-rw-r--r--
git-credential-store.html
19.42
KB
-rw-r--r--
git-credential-store.txt
2.11
KB
-rw-r--r--
git-credential.html
23.82
KB
-rw-r--r--
git-credential.txt
5.72
KB
-rw-r--r--
git-cvsexportcommit.html
21.34
KB
-rw-r--r--
git-cvsexportcommit.txt
3.13
KB
-rw-r--r--
git-cvsimport.html
27.62
KB
-rw-r--r--
git-cvsimport.txt
7.57
KB
-rw-r--r--
git-cvsserver.html
38.1
KB
-rw-r--r--
git-cvsserver.txt
15.21
KB
-rw-r--r--
git-daemon.html
32.69
KB
-rw-r--r--
git-daemon.txt
11.58
KB
-rw-r--r--
git-describe.html
24.35
KB
-rw-r--r--
git-describe.txt
5.59
KB
-rw-r--r--
git-diff-files.html
59.9
KB
-rw-r--r--
git-diff-files.txt
1.18
KB
-rw-r--r--
git-diff-index.html
64.69
KB
-rw-r--r--
git-diff-index.txt
4.49
KB
-rw-r--r--
git-diff-tree.html
82.31
KB
-rw-r--r--
git-diff-tree.txt
5.26
KB
-rw-r--r--
git-diff.html
66.63
KB
-rw-r--r--
git-diff.txt
5.34
KB
-rw-r--r--
git-difftool.html
22.93
KB
-rw-r--r--
git-difftool.txt
4.02
KB
-rw-r--r--
git-fast-export.html
23.45
KB
-rw-r--r--
git-fast-export.txt
5.16
KB
-rw-r--r--
git-fast-import.html
92.66
KB
-rw-r--r--
git-fast-import.txt
53.75
KB
-rw-r--r--
git-fetch-pack.html
21.26
KB
-rw-r--r--
git-fetch-pack.txt
3.28
KB
-rw-r--r--
git-fetch.html
38.95
KB
-rw-r--r--
git-fetch.txt
2.65
KB
-rw-r--r--
git-filter-branch.html
37.67
KB
-rw-r--r--
git-filter-branch.txt
16.84
KB
-rw-r--r--
git-fmt-merge-msg.html
19.55
KB
-rw-r--r--
git-fmt-merge-msg.txt
1.87
KB
-rw-r--r--
git-for-each-ref.html
25.45
KB
-rw-r--r--
git-for-each-ref.txt
5.72
KB
-rw-r--r--
git-format-patch.html
58.91
KB
-rw-r--r--
git-format-patch.txt
18.38
KB
-rw-r--r--
git-fsck-objects.html
16.88
KB
-rw-r--r--
git-fsck-objects.txt
354
B
-rw-r--r--
git-fsck.html
23.33
KB
-rw-r--r--
git-fsck.txt
4.54
KB
-rw-r--r--
git-gc.html
23.82
KB
-rw-r--r--
git-gc.txt
5.34
KB
-rw-r--r--
git-get-tar-commit-id.html
17.32
KB
-rw-r--r--
git-get-tar-commit-id.txt
737
B
-rw-r--r--
git-grep.html
29.02
KB
-rw-r--r--
git-grep.txt
7.55
KB
-rw-r--r--
git-gui.html
22.1
KB
-rw-r--r--
git-gui.txt
3.5
KB
-rw-r--r--
git-hash-object.html
18.92
KB
-rw-r--r--
git-hash-object.txt
1.8
KB
-rw-r--r--
git-help.html
25.14
KB
-rw-r--r--
git-help.txt
5.99
KB
-rw-r--r--
git-http-backend.html
28.46
KB
-rw-r--r--
git-http-backend.txt
9.48
KB
-rw-r--r--
git-http-fetch.html
18.41
KB
-rw-r--r--
git-http-fetch.txt
1.14
KB
-rw-r--r--
git-http-push.html
20.73
KB
-rw-r--r--
git-http-push.txt
2.91
KB
-rw-r--r--
git-imap-send.html
22.84
KB
-rw-r--r--
git-imap-send.txt
4.24
KB
-rw-r--r--
git-index-pack.html
21.01
KB
-rw-r--r--
git-index-pack.txt
3.32
KB
-rw-r--r--
git-init-db.html
16.95
KB
-rw-r--r--
git-init-db.txt
409
B
-rw-r--r--
git-init.html
23
KB
-rw-r--r--
git-init.txt
4.69
KB
-rw-r--r--
git-instaweb.html
20.06
KB
-rw-r--r--
git-instaweb.txt
2.25
KB
-rw-r--r--
git-log.html
111.87
KB
-rw-r--r--
git-log.txt
5.68
KB
-rw-r--r--
git-lost-found.html
18.83
KB
-rw-r--r--
git-lost-found.txt
1.69
KB
-rw-r--r--
git-ls-files.html
26.46
KB
-rw-r--r--
git-ls-files.txt
6.1
KB
-rw-r--r--
git-ls-remote.html
20.11
KB
-rw-r--r--
git-ls-remote.txt
2.54
KB
-rw-r--r--
git-ls-tree.html
21.06
KB
-rw-r--r--
git-ls-tree.txt
2.93
KB
-rw-r--r--
git-mailinfo.html
20.78
KB
-rw-r--r--
git-mailinfo.txt
3
KB
-rw-r--r--
git-mailsplit.html
18.52
KB
-rw-r--r--
git-mailsplit.txt
1.21
KB
-rw-r--r--
git-merge-base.html
23.17
KB
-rw-r--r--
git-merge-base.txt
4.32
KB
-rw-r--r--
git-merge-file.html
20.71
KB
-rw-r--r--
git-merge-file.txt
2.72
KB
-rw-r--r--
git-merge-index.html
19.88
KB
-rw-r--r--
git-merge-index.txt
2.39
KB
-rw-r--r--
git-merge-one-file.html
16.9
KB
-rw-r--r--
git-merge-one-file.txt
387
B
-rw-r--r--
git-merge-tree.html
17.32
KB
-rw-r--r--
git-merge-tree.txt
749
B
-rw-r--r--
git-merge.html
50.38
KB
-rw-r--r--
git-merge.txt
11.97
KB
-rw-r--r--
git-mergetool--lib.html
18.23
KB
-rw-r--r--
git-mergetool--lib.txt
1.18
KB
-rw-r--r--
git-mergetool.html
20.98
KB
-rw-r--r--
git-mergetool.txt
3.26
KB
-rw-r--r--
git-mktag.html
17.63
KB
-rw-r--r--
git-mktag.txt
806
B
-rw-r--r--
git-mktree.html
17.94
KB
-rw-r--r--
git-mktree.txt
1.05
KB
-rw-r--r--
git-mv.html
18.33
KB
-rw-r--r--
git-mv.txt
1.16
KB
-rw-r--r--
git-name-rev.html
19.17
KB
-rw-r--r--
git-name-rev.txt
1.68
KB
-rw-r--r--
git-notes.html
35.71
KB
-rw-r--r--
git-notes.txt
13.08
KB
-rw-r--r--
git-p4.html
44.35
KB
-rw-r--r--
git-p4.txt
18.73
KB
-rw-r--r--
git-pack-objects.html
28.46
KB
-rw-r--r--
git-pack-objects.txt
8.86
KB
-rw-r--r--
git-pack-redundant.html
18.24
KB
-rw-r--r--
git-pack-redundant.txt
1.13
KB
-rw-r--r--
git-pack-refs.html
19.15
KB
-rw-r--r--
git-pack-refs.txt
2.06
KB
-rw-r--r--
git-parse-remote.html
16.97
KB
-rw-r--r--
git-parse-remote.txt
471
B
-rw-r--r--
git-patch-id.html
17.71
KB
-rw-r--r--
git-patch-id.txt
940
B
-rw-r--r--
git-peek-remote.html
18.03
KB
-rw-r--r--
git-peek-remote.txt
1.08
KB
-rw-r--r--
git-prune-packed.html
17.99
KB
-rw-r--r--
git-prune-packed.txt
935
B
-rw-r--r--
git-prune.html
19.57
KB
-rw-r--r--
git-prune.txt
1.76
KB
-rw-r--r--
git-pull.html
54.96
KB
-rw-r--r--
git-pull.txt
7.72
KB
-rw-r--r--
git-push.html
48.49
KB
-rw-r--r--
git-push.txt
16.26
KB
-rw-r--r--
git-quiltimport.html
18.4
KB
-rw-r--r--
git-quiltimport.txt
1.4
KB
-rw-r--r--
git-read-tree.html
38.05
KB
-rw-r--r--
git-read-tree.txt
16.36
KB
-rw-r--r--
git-rebase.html
57.88
KB
-rw-r--r--
git-rebase.txt
23.62
KB
-rw-r--r--
git-receive-pack.html
23.98
KB
-rw-r--r--
git-receive-pack.txt
5.48
KB
-rw-r--r--
git-reflog.html
20.86
KB
-rw-r--r--
git-reflog.txt
3.09
KB
-rw-r--r--
git-relink.html
17.41
KB
-rw-r--r--
git-relink.txt
649
B
-rw-r--r--
git-remote-ext.html
22.43
KB
-rw-r--r--
git-remote-ext.txt
3.93
KB
-rw-r--r--
git-remote-fd.html
19
KB
-rw-r--r--
git-remote-fd.txt
1.63
KB
-rw-r--r--
git-remote-helpers.html
16.45
KB
-rw-r--r--
git-remote-testgit.html
17.26
KB
-rw-r--r--
git-remote-testgit.txt
570
B
-rw-r--r--
git-remote.html
26.62
KB
-rw-r--r--
git-remote.txt
6.79
KB
-rw-r--r--
git-repack.html
22.99
KB
-rw-r--r--
git-repack.txt
4.52
KB
-rw-r--r--
git-replace.html
19.86
KB
-rw-r--r--
git-replace.txt
2.26
KB
-rw-r--r--
git-repo-config.html
16.85
KB
-rw-r--r--
git-repo-config.txt
324
B
-rw-r--r--
git-request-pull.html
17.41
KB
-rw-r--r--
git-request-pull.txt
528
B
-rw-r--r--
git-rerere.html
25.93
KB
-rw-r--r--
git-rerere.txt
7.29
KB
-rw-r--r--
git-reset.html
36.54
KB
-rw-r--r--
git-reset.txt
14.15
KB
-rw-r--r--
git-rev-list.html
73.64
KB
-rw-r--r--
git-rev-list.txt
3.59
KB
-rw-r--r--
git-rev-parse.html
46.91
KB
-rw-r--r--
git-rev-parse.txt
10.03
KB
-rw-r--r--
git-revert.html
22.61
KB
-rw-r--r--
git-revert.txt
3.69
KB
-rw-r--r--
git-rm.html
24.83
KB
-rw-r--r--
git-rm.txt
5.68
KB
-rw-r--r--
git-send-email.html
36.99
KB
-rw-r--r--
git-send-email.txt
13.93
KB
-rw-r--r--
git-send-pack.html
21.8
KB
-rw-r--r--
git-send-pack.txt
3.6
KB
-rw-r--r--
git-sh-i18n--envsubst.html
17.64
KB
-rw-r--r--
git-sh-i18n--envsubst.txt
928
B
-rw-r--r--
git-sh-i18n.html
18.06
KB
-rw-r--r--
git-sh-i18n.txt
1.12
KB
-rw-r--r--
git-sh-setup.html
20.46
KB
-rw-r--r--
git-sh-setup.txt
2.73
KB
-rw-r--r--
git-shell.html
20.25
KB
-rw-r--r--
git-shell.txt
2.47
KB
-rw-r--r--
git-shortlog.html
24.29
KB
-rw-r--r--
git-shortlog.txt
2.57
KB
-rw-r--r--
git-show-branch.html
25.52
KB
-rw-r--r--
git-show-branch.txt
6.36
KB
-rw-r--r--
git-show-index.html
17.03
KB
-rw-r--r--
git-show-index.txt
478
B
-rw-r--r--
git-show-ref.html
24.15
KB
-rw-r--r--
git-show-ref.txt
5.83
KB
-rw-r--r--
git-show.html
38.73
KB
-rw-r--r--
git-show.txt
1.64
KB
-rw-r--r--
git-stage.html
16.82
KB
-rw-r--r--
git-stage.txt
300
B
-rw-r--r--
git-stash.html
29.25
KB
-rw-r--r--
git-stash.txt
9.85
KB
-rw-r--r--
git-status.html
27.38
KB
-rw-r--r--
git-status.txt
7.77
KB
-rw-r--r--
git-stripspace.html
19.37
KB
-rw-r--r--
git-stripspace.txt
1.83
KB
-rw-r--r--
git-submodule.html
36.33
KB
-rw-r--r--
git-submodule.txt
15.13
KB
-rw-r--r--
git-svn.html
73.85
KB
-rw-r--r--
git-svn.txt
41.53
KB
-rw-r--r--
git-symbolic-ref.html
19.37
KB
-rw-r--r--
git-symbolic-ref.txt
1.93
KB
-rw-r--r--
git-tag.html
31.51
KB
-rw-r--r--
git-tag.txt
9.44
KB
-rw-r--r--
git-tar-tree.html
20.04
KB
-rw-r--r--
git-tar-tree.txt
2.31
KB
-rw-r--r--
git-tools.html
22.01
KB
-rw-r--r--
git-tools.txt
3.36
KB
-rw-r--r--
git-unpack-file.html
17.13
KB
-rw-r--r--
git-unpack-file.txt
434
B
-rw-r--r--
git-unpack-objects.html
18.15
KB
-rw-r--r--
git-unpack-objects.txt
1.14
KB
-rw-r--r--
git-update-index.html
35.2
KB
-rw-r--r--
git-update-index.txt
13.2
KB
-rw-r--r--
git-update-ref.html
20.82
KB
-rw-r--r--
git-update-ref.txt
3.16
KB
-rw-r--r--
git-update-server-info.html
17.72
KB
-rw-r--r--
git-update-server-info.txt
797
B
-rw-r--r--
git-upload-archive.html
17.35
KB
-rw-r--r--
git-upload-archive.txt
617
B
-rw-r--r--
git-upload-pack.html
17.88
KB
-rw-r--r--
git-upload-pack.txt
869
B
-rw-r--r--
git-var.html
19.08
KB
-rw-r--r--
git-var.txt
1.8
KB
-rw-r--r--
git-verify-pack.html
18.39
KB
-rw-r--r--
git-verify-pack.txt
1.07
KB
-rw-r--r--
git-verify-tag.html
17.2
KB
-rw-r--r--
git-verify-tag.txt
411
B
-rw-r--r--
git-web--browse.html
21.63
KB
-rw-r--r--
git-web--browse.txt
3.43
KB
-rw-r--r--
git-whatchanged.html
35.64
KB
-rw-r--r--
git-whatchanged.txt
1.55
KB
-rw-r--r--
git-write-tree.html
17.91
KB
-rw-r--r--
git-write-tree.txt
1
KB
-rw-r--r--
git.html
70.05
KB
-rw-r--r--
git.txt
31.8
KB
-rw-r--r--
gitattributes.html
62.01
KB
-rw-r--r--
gitattributes.txt
33.51
KB
-rw-r--r--
gitcli.html
26.56
KB
-rw-r--r--
gitcli.txt
7.75
KB
-rw-r--r--
gitcore-tutorial.html
99.92
KB
-rw-r--r--
gitcore-tutorial.txt
62.33
KB
-rw-r--r--
gitcredentials.html
24.45
KB
-rw-r--r--
gitcredentials.txt
5.93
KB
-rw-r--r--
gitcvs-migration.html
26.03
KB
-rw-r--r--
gitcvs-migration.txt
7.38
KB
-rw-r--r--
gitdiffcore.html
29.51
KB
-rw-r--r--
gitdiffcore.txt
10.78
KB
-rw-r--r--
gitglossary.html
48.63
KB
-rw-r--r--
gitglossary.txt
369
B
-rw-r--r--
githooks.html
35.01
KB
-rw-r--r--
githooks.txt
13.48
KB
-rw-r--r--
gitignore.html
24.81
KB
-rw-r--r--
gitignore.txt
6.58
KB
-rw-r--r--
gitk.html
21.61
KB
-rw-r--r--
gitk.txt
3.23
KB
-rw-r--r--
gitmodules.html
21.72
KB
-rw-r--r--
gitmodules.txt
3.76
KB
-rw-r--r--
gitnamespaces.html
20.5
KB
-rw-r--r--
gitnamespaces.txt
3.2
KB
-rw-r--r--
gitremote-helpers.html
39.11
KB
-rw-r--r--
gitremote-helpers.txt
16.06
KB
-rw-r--r--
gitrepository-layout.html
28.1
KB
-rw-r--r--
gitrepository-layout.txt
7.95
KB
-rw-r--r--
gitrevisions.html
32.66
KB
-rw-r--r--
gitrevisions.txt
774
B
-rw-r--r--
gittutorial-2.html
33.55
KB
-rw-r--r--
gittutorial-2.txt
14.37
KB
-rw-r--r--
gittutorial.html
44.41
KB
-rw-r--r--
gittutorial.txt
22.43
KB
-rw-r--r--
gitweb.conf.html
66.11
KB
-rw-r--r--
gitweb.conf.txt
37.3
KB
-rw-r--r--
gitweb.html
50.94
KB
-rw-r--r--
gitweb.txt
26.34
KB
-rw-r--r--
gitworkflows.html
38.85
KB
-rw-r--r--
gitworkflows.txt
17
KB
-rw-r--r--
glossary-content.txt
21.95
KB
-rw-r--r--
howto-index.html
21.31
KB
-rw-r--r--
howto-index.txt
3.29
KB
-rw-r--r--
i18n.txt
2.16
KB
-rw-r--r--
mailmap.txt
2.35
KB
-rw-r--r--
merge-config.txt
3.47
KB
-rw-r--r--
merge-options.txt
3.58
KB
-rw-r--r--
merge-strategies.txt
4.6
KB
-rw-r--r--
mergetools-diff.txt
181
B
-rw-r--r--
mergetools-merge.txt
187
B
-rw-r--r--
pretty-formats.txt
7.59
KB
-rw-r--r--
pretty-options.txt
2.81
KB
-rw-r--r--
pull-fetch-param.txt
3.19
KB
-rw-r--r--
rev-list-options.txt
27.11
KB
-rw-r--r--
revisions.txt
11.5
KB
-rw-r--r--
sequencer.txt
392
B
-rw-r--r--
urls-remotes.txt
2.4
KB
-rw-r--r--
urls.txt
3.12
KB
-rw-r--r--
user-manual.html
264.08
KB
-rw-r--r--
user-manual.txt
170.67
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : git-notes.txt
git-notes(1) ============ NAME ---- git-notes - Add or inspect object notes SYNOPSIS -------- [verse] 'git notes' [list [<object>]] 'git notes' add [-f] [-F <file> | -m <msg> | (-c | -C) <object>] [<object>] 'git notes' copy [-f] ( --stdin | <from-object> <to-object> ) 'git notes' append [-F <file> | -m <msg> | (-c | -C) <object>] [<object>] 'git notes' edit [<object>] 'git notes' show [<object>] 'git notes' merge [-v | -q] [-s <strategy> ] <notes_ref> 'git notes' merge --commit [-v | -q] 'git notes' merge --abort [-v | -q] 'git notes' remove [--ignore-missing] [--stdin] [<object>...] 'git notes' prune [-n | -v] 'git notes' get-ref DESCRIPTION ----------- Adds, removes, or reads notes attached to objects, without touching the objects themselves. By default, notes are saved to and read from `refs/notes/commits`, but this default can be overridden. See the OPTIONS, CONFIGURATION, and ENVIRONMENT sections below. If this ref does not exist, it will be quietly created when it is first needed to store a note. A typical use of notes is to supplement a commit message without changing the commit itself. Notes can be shown by 'git log' along with the original commit message. To distinguish these notes from the message stored in the commit object, the notes are indented like the message, after an unindented line saying "Notes (<refname>):" (or "Notes:" for `refs/notes/commits`). Notes can also be added to patches prepared with `git format-patch` by using the `--notes` option. Such notes are added as a patch commentary after a three dash separator line. To change which notes are shown by 'git log', see the "notes.displayRef" configuration in linkgit:git-log[1]. See the "notes.rewrite.<command>" configuration for a way to carry notes across commands that rewrite commits. SUBCOMMANDS ----------- list:: List the notes object for a given object. If no object is given, show a list of all note objects and the objects they annotate (in the format "<note object> <annotated object>"). This is the default subcommand if no subcommand is given. add:: Add notes for a given object (defaults to HEAD). Abort if the object already has notes (use `-f` to overwrite existing notes). However, if you're using `add` interactively (using an editor to supply the notes contents), then - instead of aborting - the existing notes will be opened in the editor (like the `edit` subcommand). copy:: Copy the notes for the first object onto the second object. Abort if the second object already has notes, or if the first object has none (use -f to overwrite existing notes to the second object). This subcommand is equivalent to: `git notes add [-f] -C $(git notes list <from-object>) <to-object>` + In `--stdin` mode, take lines in the format + ---------- <from-object> SP <to-object> [ SP <rest> ] LF ---------- + on standard input, and copy the notes from each <from-object> to its corresponding <to-object>. (The optional `<rest>` is ignored so that the command can read the input given to the `post-rewrite` hook.) append:: Append to the notes of an existing object (defaults to HEAD). Creates a new notes object if needed. edit:: Edit the notes for a given object (defaults to HEAD). show:: Show the notes for a given object (defaults to HEAD). merge:: Merge the given notes ref into the current notes ref. This will try to merge the changes made by the given notes ref (called "remote") since the merge-base (if any) into the current notes ref (called "local"). + If conflicts arise and a strategy for automatically resolving conflicting notes (see the -s/--strategy option) is not given, the "manual" resolver is used. This resolver checks out the conflicting notes in a special worktree (`.git/NOTES_MERGE_WORKTREE`), and instructs the user to manually resolve the conflicts there. When done, the user can either finalize the merge with 'git notes merge --commit', or abort the merge with 'git notes merge --abort'. remove:: Remove the notes for given objects (defaults to HEAD). When giving zero or one object from the command line, this is equivalent to specifying an empty note message to the `edit` subcommand. prune:: Remove all notes for non-existing/unreachable objects. get-ref:: Print the current notes ref. This provides an easy way to retrieve the current notes ref (e.g. from scripts). OPTIONS ------- -f:: --force:: When adding notes to an object that already has notes, overwrite the existing notes (instead of aborting). -m <msg>:: --message=<msg>:: Use the given note message (instead of prompting). If multiple `-m` options are given, their values are concatenated as separate paragraphs. Lines starting with `#` and empty lines other than a single line between paragraphs will be stripped out. -F <file>:: --file=<file>:: Take the note message from the given file. Use '-' to read the note message from the standard input. Lines starting with `#` and empty lines other than a single line between paragraphs will be stripped out. -C <object>:: --reuse-message=<object>:: Take the given blob object (for example, another note) as the note message. (Use `git notes copy <object>` instead to copy notes between objects.) -c <object>:: --reedit-message=<object>:: Like '-C', but with '-c' the editor is invoked, so that the user can further edit the note message. --ref <ref>:: Manipulate the notes tree in <ref>. This overrides 'GIT_NOTES_REF' and the "core.notesRef" configuration. The ref is taken to be in `refs/notes/` if it is not qualified. --ignore-missing:: Do not consider it an error to request removing notes from an object that does not have notes attached to it. --stdin:: Also read the object names to remove notes from from the standard input (there is no reason you cannot combine this with object names from the command line). -n:: --dry-run:: Do not remove anything; just report the object names whose notes would be removed. -s <strategy>:: --strategy=<strategy>:: When merging notes, resolve notes conflicts using the given strategy. The following strategies are recognized: "manual" (default), "ours", "theirs", "union" and "cat_sort_uniq". See the "NOTES MERGE STRATEGIES" section below for more information on each notes merge strategy. --commit:: Finalize an in-progress 'git notes merge'. Use this option when you have resolved the conflicts that 'git notes merge' stored in .git/NOTES_MERGE_WORKTREE. This amends the partial merge commit created by 'git notes merge' (stored in .git/NOTES_MERGE_PARTIAL) by adding the notes in .git/NOTES_MERGE_WORKTREE. The notes ref stored in the .git/NOTES_MERGE_REF symref is updated to the resulting commit. --abort:: Abort/reset a in-progress 'git notes merge', i.e. a notes merge with conflicts. This simply removes all files related to the notes merge. -q:: --quiet:: When merging notes, operate quietly. -v:: --verbose:: When merging notes, be more verbose. When pruning notes, report all object names whose notes are removed. DISCUSSION ---------- Commit notes are blobs containing extra information about an object (usually information to supplement a commit's message). These blobs are taken from notes refs. A notes ref is usually a branch which contains "files" whose paths are the object names for the objects they describe, with some directory separators included for performance reasons footnote:[Permitted pathnames have the form 'ab'`/`'cd'`/`'ef'`/`'...'`/`'abcdef...': a sequence of directory names of two hexadecimal digits each followed by a filename with the rest of the object ID.]. Every notes change creates a new commit at the specified notes ref. You can therefore inspect the history of the notes by invoking, e.g., `git log -p notes/commits`. Currently the commit message only records which operation triggered the update, and the commit authorship is determined according to the usual rules (see linkgit:git-commit[1]). These details may change in the future. It is also permitted for a notes ref to point directly to a tree object, in which case the history of the notes can be read with `git log -p -g <refname>`. NOTES MERGE STRATEGIES ---------------------- The default notes merge strategy is "manual", which checks out conflicting notes in a special work tree for resolving notes conflicts (`.git/NOTES_MERGE_WORKTREE`), and instructs the user to resolve the conflicts in that work tree. When done, the user can either finalize the merge with 'git notes merge --commit', or abort the merge with 'git notes merge --abort'. "ours" automatically resolves conflicting notes in favor of the local version (i.e. the current notes ref). "theirs" automatically resolves notes conflicts in favor of the remote version (i.e. the given notes ref being merged into the current notes ref). "union" automatically resolves notes conflicts by concatenating the local and remote versions. "cat_sort_uniq" is similar to "union", but in addition to concatenating the local and remote versions, this strategy also sorts the resulting lines, and removes duplicate lines from the result. This is equivalent to applying the "cat | sort | uniq" shell pipeline to the local and remote versions. This strategy is useful if the notes follow a line-based format where one wants to avoid duplicated lines in the merge result. Note that if either the local or remote version contain duplicate lines prior to the merge, these will also be removed by this notes merge strategy. EXAMPLES -------- You can use notes to add annotations with information that was not available at the time a commit was written. ------------ $ git notes add -m 'Tested-by: Johannes Sixt <j6t@kdbg.org>' 72a144e2 $ git show -s 72a144e [...] Signed-off-by: Junio C Hamano <gitster@pobox.com> Notes: Tested-by: Johannes Sixt <j6t@kdbg.org> ------------ In principle, a note is a regular Git blob, and any kind of (non-)format is accepted. You can binary-safely create notes from arbitrary files using 'git hash-object': ------------ $ cc *.c $ blob=$(git hash-object -w a.out) $ git notes --ref=built add -C "$blob" HEAD ------------ (You cannot simply use `git notes --ref=built add -F a.out HEAD` because that is not binary-safe.) Of course, it doesn't make much sense to display non-text-format notes with 'git log', so if you use such notes, you'll probably need to write some special-purpose tools to do something useful with them. CONFIGURATION ------------- core.notesRef:: Notes ref to read and manipulate instead of `refs/notes/commits`. Must be an unabbreviated ref name. This setting can be overridden through the environment and command line. notes.displayRef:: Which ref (or refs, if a glob or specified more than once), in addition to the default set by `core.notesRef` or 'GIT_NOTES_REF', to read notes from when showing commit messages with the 'git log' family of commands. This setting can be overridden on the command line or by the 'GIT_NOTES_DISPLAY_REF' environment variable. See linkgit:git-log[1]. notes.rewrite.<command>:: When rewriting commits with <command> (currently `amend` or `rebase`), if this variable is `false`, git will not copy notes from the original to the rewritten commit. Defaults to `true`. See also "`notes.rewriteRef`" below. + This setting can be overridden by the 'GIT_NOTES_REWRITE_REF' environment variable. notes.rewriteMode:: When copying notes during a rewrite, what to do if the target commit already has a note. Must be one of `overwrite`, `concatenate`, and `ignore`. Defaults to `concatenate`. + This setting can be overridden with the `GIT_NOTES_REWRITE_MODE` environment variable. notes.rewriteRef:: When copying notes during a rewrite, specifies the (fully qualified) ref whose notes should be copied. May be a glob, in which case notes in all matching refs will be copied. You may also specify this configuration several times. + Does not have a default value; you must configure this variable to enable note rewriting. + Can be overridden with the 'GIT_NOTES_REWRITE_REF' environment variable. ENVIRONMENT ----------- 'GIT_NOTES_REF':: Which ref to manipulate notes from, instead of `refs/notes/commits`. This overrides the `core.notesRef` setting. 'GIT_NOTES_DISPLAY_REF':: Colon-delimited list of refs or globs indicating which refs, in addition to the default from `core.notesRef` or 'GIT_NOTES_REF', to read notes from when showing commit messages. This overrides the `notes.displayRef` setting. + A warning will be issued for refs that do not exist, but a glob that does not match any refs is silently ignored. 'GIT_NOTES_REWRITE_MODE':: When copying notes during a rewrite, what to do if the target commit already has a note. Must be one of `overwrite`, `concatenate`, and `ignore`. This overrides the `core.rewriteMode` setting. 'GIT_NOTES_REWRITE_REF':: When rewriting commits, which notes to copy from the original to the rewritten commit. Must be a colon-delimited list of refs or globs. + If not set in the environment, the list of notes to copy depends on the `notes.rewrite.<command>` and `notes.rewriteRef` settings. Author ------ Written by Johannes Schindelin <johannes.schindelin@gmx.de> and Johan Herland <johan@herland.net> Documentation ------------- Documentation by Johannes Schindelin and Johan Herland GIT --- Part of the linkgit:git[7] suite
Close