/
usr
/
share
/
doc
/
git
/
/usr/share/doc/git
mkdir
upload
Name
Size
Mode
Actions
contrib/
-
0755
rm
howto/
-
0755
rm
RelNotes/
-
0755
rm
technical/
-
0755
rm
blame-options.txt
6001
0644
edit
dl
rm
cmds-ancillaryinterrogators.txt
1294
0644
edit
dl
rm
cmds-ancillarymanipulators.txt
746
0644
edit
dl
rm
cmds-developerinterfaces.txt
678
0644
edit
dl
rm
cmds-foreignscminterface.txt
399
0644
edit
dl
rm
cmds-guide.txt
833
0644
edit
dl
rm
cmds-mainporcelain.txt
3033
0644
edit
dl
rm
cmds-plumbinginterrogators.txt
1539
0644
edit
dl
rm
cmds-plumbingmanipulators.txt
1410
0644
edit
dl
rm
cmds-purehelpers.txt
1268
0644
edit
dl
rm
cmds-synchelpers.txt
449
0644
edit
dl
rm
cmds-synchingrepositories.txt
397
0644
edit
dl
rm
cmds-userinterfaces.txt
507
0644
edit
dl
rm
CODE_OF_CONDUCT.md
5989
0644
edit
dl
rm
config.txt
18001
0644
edit
dl
rm
date-formats.txt
1172
0644
edit
dl
rm
diff-format.txt
6573
0644
edit
dl
rm
diff-generate-patch.txt
7253
0644
edit
dl
rm
diff-options.txt
32436
0644
edit
dl
rm
docbook-xsl.css
4557
0644
edit
dl
rm
everyday.html
16996
0644
edit
dl
rm
fetch-options.txt
12281
0644
edit
dl
rm
fsck-msgids.txt
4197
0644
edit
dl
rm
git-add.html
40369
0644
edit
dl
rm
git-add.txt
16164
0644
edit
dl
rm
git-am.html
33161
0644
edit
dl
rm
git-am.txt
9317
0644
edit
dl
rm
git-annotate.html
28391
0644
edit
dl
rm
git-annotate.txt
771
0644
edit
dl
rm
git-apply.html
33407
0644
edit
dl
rm
git-apply.txt
10950
0644
edit
dl
rm
git-archive.html
29856
0644
edit
dl
rm
git-archive.txt
8491
0644
edit
dl
rm
git-bisect-lk2009.html
81243
0644
edit
dl
rm
git-bisect-lk2009.txt
49694
0644
edit
dl
rm
git-bisect.html
40572
0644
edit
dl
rm
git-bisect.txt
17905
0644
edit
dl
rm
git-blame.html
42501
0644
edit
dl
rm
git-blame.txt
8732
0644
edit
dl
rm
git-branch.html
48253
0644
edit
dl
rm
git-branch.txt
15748
0644
edit
dl
rm
git-bugreport.html
20509
0644
edit
dl
rm
git-bugreport.txt
2421
0644
edit
dl
rm
git-bundle.html
33269
0644
edit
dl
rm
git-bundle.txt
11703
0644
edit
dl
rm
git-cat-file.html
38661
0644
edit
dl
rm
git-cat-file.txt
13615
0644
edit
dl
rm
git-check-attr.html
22633
0644
edit
dl
rm
git-check-attr.txt
3390
0644
edit
dl
rm
git-check-ignore.html
23135
0644
edit
dl
rm
git-check-ignore.txt
4156
0644
edit
dl
rm
git-check-mailmap.html
18816
0644
edit
dl
rm
git-check-mailmap.txt
1108
0644
edit
dl
rm
git-check-ref-format.html
24040
0644
edit
dl
rm
git-check-ref-format.txt
5034
0644
edit
dl
rm
git-checkout-index.html
25362
0644
edit
dl
rm
git-checkout-index.txt
5669
0644
edit
dl
rm
git-checkout.html
52719
0644
edit
dl
rm
git-checkout.txt
22362
0644
edit
dl
rm
git-cherry-pick.html
31065
0644
edit
dl
rm
git-cherry-pick.txt
8764
0644
edit
dl
rm
git-cherry.html
22423
0644
edit
dl
rm
git-cherry.txt
3615
0644
edit
dl
rm
git-clean.html
23981
0644
edit
dl
rm
git-clean.txt
4523
0644
edit
dl
rm
git-clone.html
44328
0644
edit
dl
rm
git-clone.txt
14772
0644
edit
dl
rm
git-column.html
23317
0644
edit
dl
rm
git-column.txt
2201
0644
edit
dl
rm
git-commit-graph.html
26147
0644
edit
dl
rm
git-commit-graph.txt
5949
0644
edit
dl
rm
git-commit-tree.html
26683
0644
edit
dl
rm
git-commit-tree.txt
2710
0644
edit
dl
rm
git-commit.html
57154
0644
edit
dl
rm
git-commit.txt
21575
0644
edit
dl
rm
git-config.html
415540
0644
edit
dl
rm
git-config.txt
19755
0644
edit
dl
rm
git-contacts.html
20718
0644
edit
dl
rm
git-contacts.txt
2584
0644
edit
dl
rm
git-count-objects.html
18946
0644
edit
dl
rm
git-count-objects.txt
1350
0644
edit
dl
rm
git-credential-cache--daemon.html
18182
0644
edit
dl
rm
git-credential-cache--daemon.txt
891
0644
edit
dl
rm
git-credential-cache.html
20180
0644
edit
dl
rm
git-credential-cache.txt
2484
0644
edit
dl
rm
git-credential-store.html
22043
0644
edit
dl
rm
git-credential-store.txt
3637
0644
edit
dl
rm
git-credential.html
26676
0644
edit
dl
rm
git-credential.txt
7327
0644
edit
dl
rm
git-describe.html
28268
0644
edit
dl
rm
git-describe.txt
8319
0644
edit
dl
rm
git-diagnose.html
20157
0644
edit
dl
rm
git-diagnose.txt
2208
0644
edit
dl
rm
git-diff-files.html
79130
0644
edit
dl
rm
git-diff-files.txt
1225
0644
edit
dl
rm
git-diff-index.html
84351
0644
edit
dl
rm
git-diff-index.txt
4811
0644
edit
dl
rm
git-diff-tree.html
116052
0644
edit
dl
rm
git-diff-tree.txt
4184
0644
edit
dl
rm
git-diff.html
107093
0644
edit
dl
rm
git-diff.txt
8039
0644
edit
dl
rm
git-difftool.html
27048
0644
edit
dl
rm
git-difftool.txt
4624
0644
edit
dl
rm
git-fast-export.html
31650
0644
edit
dl
rm
git-fast-export.txt
11282
0644
edit
dl
rm
git-fast-import.html
103283
0644
edit
dl
rm
git-fast-import.txt
59963
0644
edit
dl
rm
git-fetch-pack.html
23255
0644
edit
dl
rm
git-fetch-pack.txt
4248
0644
edit
dl
rm
git-fetch.html
75456
0644
edit
dl
rm
git-fetch.txt
11812
0644
edit
dl
rm
git-filter-branch.html
54648
0644
edit
dl
rm
git-filter-branch.txt
31031
0644
edit
dl
rm
git-fmt-merge-msg.html
21435
0644
edit
dl
rm
git-fmt-merge-msg.txt
1931
0644
edit
dl
rm
git-for-each-ref.html
43438
0644
edit
dl
rm
git-for-each-ref.txt
17073
0644
edit
dl
rm
git-for-each-repo.html
19296
0644
edit
dl
rm
git-for-each-repo.txt
1543
0644
edit
dl
rm
git-format-patch.html
81842
0644
edit
dl
rm
git-format-patch.txt
28876
0644
edit
dl
rm
git-fsck-objects.html
17392
0644
edit
dl
rm
git-fsck-objects.txt
354
0644
edit
dl
rm
git-fsck.html
39162
0644
edit
dl
rm
git-fsck.txt
5882
0644
edit
dl
rm
git-fsmonitor--daemon.html
22875
0644
edit
dl
rm
git-fsmonitor--daemon.txt
3610
0644
edit
dl
rm
git-gc.html
36697
0644
edit
dl
rm
git-gc.txt
6292
0644
edit
dl
rm
git-get-tar-commit-id.html
17835
0644
edit
dl
rm
git-get-tar-commit-id.txt
753
0644
edit
dl
rm
git-grep.html
36030
0644
edit
dl
rm
git-grep.txt
10763
0644
edit
dl
rm
git-hash-object.html
19939
0644
edit
dl
rm
git-hash-object.txt
2142
0644
edit
dl
rm
git-help.html
28141
0644
edit
dl
rm
git-help.txt
7527
0644
edit
dl
rm
git-hook.html
18807
0644
edit
dl
rm
git-hook.txt
1028
0644
edit
dl
rm
git-http-backend.html
30974
0644
edit
dl
rm
git-http-backend.txt
11472
0644
edit
dl
rm
git-http-fetch.html
19679
0644
edit
dl
rm
git-http-fetch.txt
1775
0644
edit
dl
rm
git-http-push.html
21391
0644
edit
dl
rm
git-http-push.txt
2995
0644
edit
dl
rm
git-imap-send.html
25472
0644
edit
dl
rm
git-imap-send.txt
3567
0644
edit
dl
rm
git-index-pack.html
24735
0644
edit
dl
rm
git-index-pack.txt
5205
0644
edit
dl
rm
git-init-db.html
17460
0644
edit
dl
rm
git-init-db.txt
409
0644
edit
dl
rm
git-init.html
26604
0644
edit
dl
rm
git-init.txt
5869
0644
edit
dl
rm
git-interpret-trailers.html
42006
0644
edit
dl
rm
git-interpret-trailers.txt
18579
0644
edit
dl
rm
git-log.html
182485
0644
edit
dl
rm
git-log.txt
6864
0644
edit
dl
rm
git-ls-files.html
35053
0644
edit
dl
rm
git-ls-files.txt
11622
0644
edit
dl
rm
git-ls-remote.html
24349
0644
edit
dl
rm
git-ls-remote.txt
4841
0644
edit
dl
rm
git-ls-tree.html
25628
0644
edit
dl
rm
git-ls-tree.txt
5515
0644
edit
dl
rm
git-mailinfo.html
23402
0644
edit
dl
rm
git-mailinfo.txt
3866
0644
edit
dl
rm
git-mailsplit.html
19264
0644
edit
dl
rm
git-mailsplit.txt
1342
0644
edit
dl
rm
git-maintenance.html
46000
0644
edit
dl
rm
git-maintenance.txt
18901
0644
edit
dl
rm
git-merge-base.html
28380
0644
edit
dl
rm
git-merge-base.txt
7759
0644
edit
dl
rm
git-merge-file.html
22656
0644
edit
dl
rm
git-merge-file.txt
3718
0644
edit
dl
rm
git-merge-index.html
20450
0644
edit
dl
rm
git-merge-index.txt
2445
0644
edit
dl
rm
git-merge-one-file.html
17416
0644
edit
dl
rm
git-merge-one-file.txt
387
0644
edit
dl
rm
git-merge-tree.html
33496
0644
edit
dl
rm
git-merge-tree.txt
11923
0644
edit
dl
rm
git-merge.html
71005
0644
edit
dl
rm
git-merge.txt
15068
0644
edit
dl
rm
git-mergetool--lib.html
19127
0644
edit
dl
rm
git-mergetool--lib.txt
1467
0644
edit
dl
rm
git-mergetool.html
39795
0644
edit
dl
rm
git-mergetool.txt
4473
0644
edit
dl
rm
git-mktag.html
19819
0644
edit
dl
rm
git-mktag.txt
1782
0644
edit
dl
rm
git-mktree.html
18474
0644
edit
dl
rm
git-mktree.txt
1075
0644
edit
dl
rm
git-multi-pack-index.html
23595
0644
edit
dl
rm
git-multi-pack-index.txt
4632
0644
edit
dl
rm
git-mv.html
20092
0644
edit
dl
rm
git-mv.txt
2103
0644
edit
dl
rm
git-name-rev.html
21670
0644
edit
dl
rm
git-name-rev.txt
3352
0644
edit
dl
rm
git-notes.html
41046
0644
edit
dl
rm
git-notes.txt
13866
0644
edit
dl
rm
git-pack-objects.html
42391
0644
edit
dl
rm
git-pack-objects.txt
19297
0644
edit
dl
rm
git-pack-redundant.html
19799
0644
edit
dl
rm
git-pack-redundant.txt
1876
0644
edit
dl
rm
git-pack-refs.html
21120
0644
edit
dl
rm
git-pack-refs.txt
3136
0644
edit
dl
rm
git-patch-id.html
20354
0644
edit
dl
rm
git-patch-id.txt
2430
0644
edit
dl
rm
git-prune-packed.html
18539
0644
edit
dl
rm
git-prune-packed.txt
946
0644
edit
dl
rm
git-prune.html
20327
0644
edit
dl
rm
git-prune.txt
1919
0644
edit
dl
rm
git-pull.html
77070
0644
edit
dl
rm
git-pull.txt
8354
0644
edit
dl
rm
git-push.html
74993
0644
edit
dl
rm
git-push.txt
28061
0644
edit
dl
rm
git-quiltimport.html
19466
0644
edit
dl
rm
git-quiltimport.txt
1693
0644
edit
dl
rm
git-range-diff.html
31673
0644
edit
dl
rm
git-range-diff.txt
10337
0644
edit
dl
rm
git-read-tree.html
39078
0644
edit
dl
rm
git-read-tree.txt
16897
0644
edit
dl
rm
git-rebase.html
98945
0644
edit
dl
rm
git-rebase.txt
47228
0644
edit
dl
rm
git-receive-pack.html
30448
0644
edit
dl
rm
git-receive-pack.txt
9526
0644
edit
dl
rm
git-reflog.html
23514
0644
edit
dl
rm
git-reflog.txt
4575
0644
edit
dl
rm
git-remote-ext.html
23012
0644
edit
dl
rm
git-remote-ext.txt
3977
0644
edit
dl
rm
git-remote-fd.html
19501
0644
edit
dl
rm
git-remote-fd.txt
1628
0644
edit
dl
rm
git-remote-helpers.html
16974
0644
edit
dl
rm
git-remote.html
29903
0644
edit
dl
rm
git-remote.txt
8768
0644
edit
dl
rm
git-repack.html
32819
0644
edit
dl
rm
git-repack.txt
11020
0644
edit
dl
rm
git-replace.html
24858
0644
edit
dl
rm
git-replace.txt
5211
0644
edit
dl
rm
git-request-pull.html
20295
0644
edit
dl
rm
git-request-pull.txt
2035
0644
edit
dl
rm
git-rerere.html
27040
0644
edit
dl
rm
git-rerere.txt
7781
0644
edit
dl
rm
git-reset.html
44520
0644
edit
dl
rm
git-reset.txt
19125
0644
edit
dl
rm
git-restore.html
28166
0644
edit
dl
rm
git-restore.txt
7082
0644
edit
dl
rm
git-rev-list.html
118128
0644
edit
dl
rm
git-rev-list.txt
3220
0644
edit
dl
rm
git-rev-parse.html
64641
0644
edit
dl
rm
git-rev-parse.txt
15840
0644
edit
dl
rm
git-revert.html
26792
0644
edit
dl
rm
git-revert.txt
5421
0644
edit
dl
rm
git-rm.html
27584
0644
edit
dl
rm
git-rm.txt
7236
0644
edit
dl
rm
git-send-pack.html
24576
0644
edit
dl
rm
git-send-pack.txt
5160
0644
edit
dl
rm
git-sh-i18n--envsubst.html
18166
0644
edit
dl
rm
git-sh-i18n--envsubst.txt
928
0644
edit
dl
rm
git-sh-i18n.html
18595
0644
edit
dl
rm
git-sh-i18n.txt
1147
0644
edit
dl
rm
git-sh-setup.html
21277
0644
edit
dl
rm
git-sh-setup.txt
2976
0644
edit
dl
rm
git-shell.html
21414
0644
edit
dl
rm
git-shell.txt
2981
0644
edit
dl
rm
git-shortlog.html
64618
0644
edit
dl
rm
git-shortlog.txt
4409
0644
edit
dl
rm
git-show-branch.html
26813
0644
edit
dl
rm
git-show-branch.txt
6589
0644
edit
dl
rm
git-show-index.html
19521
0644
edit
dl
rm
git-show-index.txt
1473
0644
edit
dl
rm
git-show-ref.html
26075
0644
edit
dl
rm
git-show-ref.txt
6648
0644
edit
dl
rm
git-show.html
111644
0644
edit
dl
rm
git-show.txt
1929
0644
edit
dl
rm
git-sparse-checkout.html
43949
0644
edit
dl
rm
git-sparse-checkout.txt
21258
0644
edit
dl
rm
git-stage.html
17341
0644
edit
dl
rm
git-stage.txt
299
0644
edit
dl
rm
git-stash.html
38594
0644
edit
dl
rm
git-stash.txt
14999
0644
edit
dl
rm
git-status.html
45718
0644
edit
dl
rm
git-status.txt
20295
0644
edit
dl
rm
git-stripspace.html
20016
0644
edit
dl
rm
git-stripspace.txt
1946
0644
edit
dl
rm
git-submodule.html
45581
0644
edit
dl
rm
git-submodule.txt
20819
0644
edit
dl
rm
git-subtree.html
36823
0644
edit
dl
rm
git-subtree.txt
13687
0644
edit
dl
rm
git-switch.html
33314
0644
edit
dl
rm
git-switch.txt
8607
0644
edit
dl
rm
git-symbolic-ref.html
20452
0644
edit
dl
rm
git-symbolic-ref.txt
2327
0644
edit
dl
rm
git-tag.html
38958
0644
edit
dl
rm
git-tag.txt
13469
0644
edit
dl
rm
git-tools.html
17207
0644
edit
dl
rm
git-tools.txt
422
0644
edit
dl
rm
git-unpack-file.html
17645
0644
edit
dl
rm
git-unpack-file.txt
434
0644
edit
dl
rm
git-unpack-objects.html
18811
0644
edit
dl
rm
git-unpack-objects.txt
1220
0644
edit
dl
rm
git-update-index.html
49723
0644
edit
dl
rm
git-update-index.txt
23928
0644
edit
dl
rm
git-update-ref.html
25909
0644
edit
dl
rm
git-update-ref.txt
6298
0644
edit
dl
rm
git-update-server-info.html
18255
0644
edit
dl
rm
git-update-server-info.txt
801
0644
edit
dl
rm
git-upload-archive.html
19776
0644
edit
dl
rm
git-upload-archive.txt
2087
0644
edit
dl
rm
git-upload-pack.html
21671
0644
edit
dl
rm
git-upload-pack.txt
2998
0644
edit
dl
rm
git-var.html
21537
0644
edit
dl
rm
git-var.txt
3176
0644
edit
dl
rm
git-verify-commit.html
17948
0644
edit
dl
rm
git-verify-commit.txt
575
0644
edit
dl
rm
git-verify-pack.html
18953
0644
edit
dl
rm
git-verify-pack.txt
1111
0644
edit
dl
rm
git-verify-tag.html
17941
0644
edit
dl
rm
git-verify-tag.txt
562
0644
edit
dl
rm
git-version.html
17798
0644
edit
dl
rm
git-version.txt
532
0644
edit
dl
rm
git-web--browse.html
22405
0644
edit
dl
rm
git-web--browse.txt
3576
0644
edit
dl
rm
git-whatchanged.html
18572
0644
edit
dl
rm
git-whatchanged.txt
1098
0644
edit
dl
rm
git-worktree.html
46341
0644
edit
dl
rm
git-worktree.txt
20985
0644
edit
dl
rm
git-write-tree.html
18441
0644
edit
dl
rm
git-write-tree.txt
1026
0644
edit
dl
rm
git.html
107237
0644
edit
dl
rm
git.txt
43254
0644
edit
dl
rm
gitattributes.html
82845
0644
edit
dl
rm
gitattributes.txt
49511
0644
edit
dl
rm
gitcli.html
29584
0644
edit
dl
rm
gitcli.txt
9697
0644
edit
dl
rm
gitcore-tutorial.html
100139
0644
edit
dl
rm
gitcore-tutorial.txt
62240
0644
edit
dl
rm
gitcredentials.html
31980
0644
edit
dl
rm
gitcredentials.txt
11317
0644
edit
dl
rm
gitdiffcore.html
33745
0644
edit
dl
rm
gitdiffcore.txt
14082
0644
edit
dl
rm
giteveryday.html
38092
0644
edit
dl
rm
giteveryday.txt
14422
0644
edit
dl
rm
gitfaq.html
44081
0644
edit
dl
rm
gitfaq.txt
21069
0644
edit
dl
rm
gitformat-bundle.html
21446
0644
edit
dl
rm
gitformat-bundle.txt
3256
0644
edit
dl
rm
gitformat-chunk.html
24329
0644
edit
dl
rm
gitformat-chunk.txt
5560
0644
edit
dl
rm
gitformat-commit-graph.html
28630
0644
edit
dl
rm
gitformat-commit-graph.txt
7857
0644
edit
dl
rm
gitformat-index.html
40269
0644
edit
dl
rm
gitformat-index.txt
15180
0644
edit
dl
rm
gitformat-pack.html
49811
0644
edit
dl
rm
gitformat-pack.txt
23509
0644
edit
dl
rm
gitformat-signature.html
27362
0644
edit
dl
rm
gitformat-signature.txt
8093
0644
edit
dl
rm
gitglossary.html
64201
0644
edit
dl
rm
gitglossary.txt
358
0644
edit
dl
rm
githooks.html
56500
0644
edit
dl
rm
githooks.txt
29331
0644
edit
dl
rm
gitignore.html
28399
0644
edit
dl
rm
gitignore.txt
8918
0644
edit
dl
rm
gitmailmap.html
22819
0644
edit
dl
rm
gitmailmap.txt
3551
0644
edit
dl
rm
gitmodules.html
24057
0644
edit
dl
rm
gitmodules.txt
4800
0644
edit
dl
rm
gitnamespaces.html
22148
0644
edit
dl
rm
gitnamespaces.txt
2509
0644
edit
dl
rm
gitprotocol-capabilities.html
37425
0644
edit
dl
rm
gitprotocol-capabilities.txt
15311
0644
edit
dl
rm
gitprotocol-common.html
21565
0644
edit
dl
rm
gitprotocol-common.txt
3177
0644
edit
dl
rm
gitprotocol-http.html
43234
0644
edit
dl
rm
gitprotocol-http.txt
17994
0644
edit
dl
rm
gitprotocol-pack.html
53023
0644
edit
dl
rm
gitprotocol-pack.txt
27678
0644
edit
dl
rm
gitprotocol-v2.html
59690
0644
edit
dl
rm
gitprotocol-v2.txt
31434
0644
edit
dl
rm
gitremote-helpers.html
48215
0644
edit
dl
rm
gitremote-helpers.txt
21785
0644
edit
dl
rm
gitrepository-layout.html
39352
0644
edit
dl
rm
gitrepository-layout.txt
11622
0644
edit
dl
rm
gitrevisions.html
41621
0644
edit
dl
rm
gitrevisions.txt
823
0644
edit
dl
rm
gitsubmodules.html
31699
0644
edit
dl
rm
gitsubmodules.txt
10366
0644
edit
dl
rm
gittutorial-2.html
34547
0644
edit
dl
rm
gittutorial-2.txt
14750
0644
edit
dl
rm
gittutorial.html
46263
0644
edit
dl
rm
gittutorial.txt
22972
0644
edit
dl
rm
gitworkflows.html
39869
0644
edit
dl
rm
gitworkflows.txt
17414
0644
edit
dl
rm
glossary-content.txt
32609
0644
edit
dl
rm
howto-index.html
22991
0644
edit
dl
rm
howto-index.txt
4001
0644
edit
dl
rm
i18n.txt
2940
0644
edit
dl
rm
line-range-format.txt
1162
0644
edit
dl
rm
line-range-options.txt
761
0644
edit
dl
rm
merge-options.txt
7236
0644
edit
dl
rm
merge-strategies.txt
6610
0644
edit
dl
rm
mergetools-diff.txt
1507
0644
edit
dl
rm
mergetools-merge.txt
2586
0644
edit
dl
rm
MyFirstContribution.html
90572
0644
edit
dl
rm
MyFirstContribution.txt
54596
0644
edit
dl
rm
MyFirstObjectWalk.html
60554
0644
edit
dl
rm
MyFirstObjectWalk.txt
28979
0644
edit
dl
rm
object-format-disclaimer.txt
470
0644
edit
dl
rm
pretty-formats.txt
15669
0644
edit
dl
rm
pretty-options.txt
4201
0644
edit
dl
rm
pull-fetch-param.txt
5476
0644
edit
dl
rm
README.md
3652
0644
edit
dl
rm
ref-reachability-filters.txt
391
0644
edit
dl
rm
rerere-options.txt
414
0644
edit
dl
rm
rev-list-description.txt
2531
0644
edit
dl
rm
rev-list-options.txt
46906
0644
edit
dl
rm
ReviewingGuidelines.html
26831
0644
edit
dl
rm
ReviewingGuidelines.txt
8100
0644
edit
dl
rm
revisions.txt
17109
0644
edit
dl
rm
scalar.html
26055
0644
edit
dl
rm
scalar.txt
6056
0644
edit
dl
rm
sequencer.txt
472
0644
edit
dl
rm
signoff-option.txt
781
0644
edit
dl
rm
SubmittingPatches.html
55660
0644
edit
dl
rm
SubmittingPatches.txt
30147
0644
edit
dl
rm
ToolsForGit.html
19020
0644
edit
dl
rm
ToolsForGit.txt
1348
0644
edit
dl
rm
trace2-target-values.txt
529
0644
edit
dl
rm
transfer-data-leaks.txt
1712
0644
edit
dl
rm
urls-remotes.txt
2642
0644
edit
dl
rm
urls.txt
3634
0644
edit
dl
rm
user-manual.html
275731
0644
edit
dl
rm
user-manual.txt
173518
0644
edit
dl
rm
Edit:
/usr/share/doc/git/git-notes.txt
(13866B)
git-notes(1) ============ NAME ---- git-notes - Add or inspect object notes SYNOPSIS -------- [verse] 'git notes' [list [<object>]] 'git notes' add [-f] [--allow-empty] [--[no-]separator | --separator=<paragraph-break>] [--[no-]stripspace] [-F <file> | -m <msg> | (-c | -C) <object>] [<object>] 'git notes' copy [-f] ( --stdin | <from-object> [<to-object>] ) 'git notes' append [--allow-empty] [--[no-]separator | --separator=<paragraph-break>] [--[no-]stripspace] [-F <file> | -m <msg> | (-c | -C) <object>] [<object>] 'git notes' edit [--allow-empty] [<object>] [--[no-]stripspace] '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" discussion in <<CONFIGURATION>>. 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). If you specify multiple `-m` and `-F`, a blank line will be inserted between the messages. Use the `--separator` option to insert other delimiters. copy:: Copy the notes for the first object onto the second object (defaults to HEAD). 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 new message(s) given by `-m` or `-F` options to an existing note, or add them as a new note if one does not exist, for the object (defaults to HEAD). When appending to an existing note, a blank line is added before each new message as an inter-paragraph separator. The separator can be customized with the `--separator` option. 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 "NOTES MERGE STRATEGIES" section) 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. If you wish to keep them verbatim, use `--no-stripspace`. -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. If you wish to keep them verbatim, use `--no-stripspace`. -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.). By default, message will be copied verbatim, but if you wish to strip out the lines starting with `#` and empty lines other than a single line between paragraphs, use with`--stripspace` option. -c <object>:: --reedit-message=<object>:: Like '-C', but with `-c` the editor is invoked, so that the user can further edit the note message. --allow-empty:: Allow an empty note object to be stored. The default behavior is to automatically remove empty notes. --[no-]separator, --separator=<paragraph-break>:: Specify a string used as a custom inter-paragraph separator (a newline is added at the end as needed). If `--no-separator`, no separators will be added between paragraphs. Defaults to a blank line. --[no-]stripspace:: Strip leading and trailing whitespace from the note message. Also strip out empty lines other than a single line between paragraphs. Lines starting with `#` will be stripped out in non-editor cases like `-m`, `-F` and `-C`, but not in editor case like `git notes edit`, `-c`, etc. --ref <ref>:: Manipulate the notes tree in <ref>. This overrides `GIT_NOTES_REF` and the "core.notesRef" configuration. The ref specifies the full refname when it begins with `refs/notes/`; when it begins with `notes/`, `refs/` and otherwise `refs/notes/` is prefixed to form a full name of the ref. --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 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". This option overrides the "notes.mergeStrategy" configuration setting. 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 an 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 'bf'`/`'fe'`/`'30'`/`'...'`/`'680d5a...': 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'. Users may select an automated merge strategy from among the following using either -s/--strategy option or configuring notes.mergeStrategy accordingly: "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 --allow-empty -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]] 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. include::includes/cmd-config-section-rest.txt[] include::config/notes.txt[] 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`, `cat_sort_uniq`, or `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. GIT --- Part of the linkgit:git[1] suite
Save
git-notes(1) ============ NAME ---- git-notes - Add or inspect object notes SYNOPSIS -------- [verse] 'git notes' [list [
]] 'git notes' add [-f] [--allow-empty] [--[no-]separator | --separator=
] [--[no-]stripspace] [-F
| -m
| (-c | -C)
] [
] 'git notes' copy [-f] ( --stdin |
[
] ) 'git notes' append [--allow-empty] [--[no-]separator | --separator=
] [--[no-]stripspace] [-F
| -m
| (-c | -C)
] [
] 'git notes' edit [--allow-empty] [
] [--[no-]stripspace] 'git notes' show [
] 'git notes' merge [-v | -q] [-s
]
'git notes' merge --commit [-v | -q] 'git notes' merge --abort [-v | -q] 'git notes' remove [--ignore-missing] [--stdin] [
...] '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 (
):" (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" discussion in <
>. See the "notes.rewrite.
" 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 "
"). 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). If you specify multiple `-m` and `-F`, a blank line will be inserted between the messages. Use the `--separator` option to insert other delimiters. copy:: Copy the notes for the first object onto the second object (defaults to HEAD). 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
)
` + In `--stdin` mode, take lines in the format + ----------
SP
[ SP
] LF ---------- + on standard input, and copy the notes from each
to its corresponding
. (The optional `
` is ignored so that the command can read the input given to the `post-rewrite` hook.) append:: Append new message(s) given by `-m` or `-F` options to an existing note, or add them as a new note if one does not exist, for the object (defaults to HEAD). When appending to an existing note, a blank line is added before each new message as an inter-paragraph separator. The separator can be customized with the `--separator` option. 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 "NOTES MERGE STRATEGIES" section) 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
:: --message=
:: 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. If you wish to keep them verbatim, use `--no-stripspace`. -F
:: --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. If you wish to keep them verbatim, use `--no-stripspace`. -C
:: --reuse-message=
:: Take the given blob object (for example, another note) as the note message. (Use `git notes copy
` instead to copy notes between objects.). By default, message will be copied verbatim, but if you wish to strip out the lines starting with `#` and empty lines other than a single line between paragraphs, use with`--stripspace` option. -c
:: --reedit-message=
:: Like '-C', but with `-c` the editor is invoked, so that the user can further edit the note message. --allow-empty:: Allow an empty note object to be stored. The default behavior is to automatically remove empty notes. --[no-]separator, --separator=
:: Specify a string used as a custom inter-paragraph separator (a newline is added at the end as needed). If `--no-separator`, no separators will be added between paragraphs. Defaults to a blank line. --[no-]stripspace:: Strip leading and trailing whitespace from the note message. Also strip out empty lines other than a single line between paragraphs. Lines starting with `#` will be stripped out in non-editor cases like `-m`, `-F` and `-C`, but not in editor case like `git notes edit`, `-c`, etc. --ref
:: Manipulate the notes tree in
. This overrides `GIT_NOTES_REF` and the "core.notesRef" configuration. The ref specifies the full refname when it begins with `refs/notes/`; when it begins with `notes/`, `refs/` and otherwise `refs/notes/` is prefixed to form a full name of the ref. --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 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=
:: When merging notes, resolve notes conflicts using the given strategy. The following strategies are recognized: "manual" (default), "ours", "theirs", "union" and "cat_sort_uniq". This option overrides the "notes.mergeStrategy" configuration setting. 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 an 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 'bf'`/`'fe'`/`'30'`/`'...'`/`'680d5a...': 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
`. 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'. Users may select an automated merge strategy from among the following using either -s/--strategy option or configuring notes.mergeStrategy accordingly: "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
' 72a144e2 $ git show -s 72a144e [...] Signed-off-by: Junio C Hamano
Notes: Tested-by: Johannes Sixt
------------ 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 --allow-empty -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]] 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. include::includes/cmd-config-section-rest.txt[] include::config/notes.txt[] 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`, `cat_sort_uniq`, or `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.
` and `notes.rewriteRef` settings. GIT --- Part of the linkgit:git[1] suite