config.txt: move fetch part out to a separate file
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Nguyễn Thái Ngọc Duy committed
Aug 22, 2018 at 18:05 UTC
ca0e61c09fa5e5a7b6b60d985fb8b77f6f183cc4
2 files changed
+66
-65
Documentation/config.txt
+1
-65
@@ -1507,71 +1507,7 @@ fastimport.unpackLimit::
1507
operation complete faster, especially on slow filesystems. If
1508
not set, the value of `transfer.unpackLimit` is used instead.
1509
1510
-fetch.recurseSubmodules::
1511
- This option can be either set to a boolean value or to 'on-demand'.
1512
- Setting it to a boolean changes the behavior of fetch and pull to
1513
- unconditionally recurse into submodules when set to true or to not
1514
- recurse at all when set to false. When set to 'on-demand' (the default
1515
- value), fetch and pull will only recurse into a populated submodule
1516
- when its superproject retrieves a commit that updates the submodule's
1517
- reference.
1518
-
1519
-fetch.fsckObjects::
1520
- If it is set to true, git-fetch-pack will check all fetched
1521
- objects. See `transfer.fsckObjects` for what's
1522
- checked. Defaults to false. If not set, the value of
1523
- `transfer.fsckObjects` is used instead.
1524
-
1525
-fetch.fsck.<msg-id>::
1526
- Acts like `fsck.<msg-id>`, but is used by
1527
- linkgit:git-fetch-pack[1] instead of linkgit:git-fsck[1]. See
1528
- the `fsck.<msg-id>` documentation for details.
1529
-
1530
-fetch.fsck.skipList::
1531
- Acts like `fsck.skipList`, but is used by
1532
- linkgit:git-fetch-pack[1] instead of linkgit:git-fsck[1]. See
1533
- the `fsck.skipList` documentation for details.
1534
-
1535
-fetch.unpackLimit::
1536
- If the number of objects fetched over the Git native
1537
- transfer is below this
1538
- limit, then the objects will be unpacked into loose object
1539
- files. However if the number of received objects equals or
1540
- exceeds this limit then the received pack will be stored as
1541
- a pack, after adding any missing delta bases. Storing the
1542
- pack from a push can make the push operation complete faster,
1543
- especially on slow filesystems. If not set, the value of
1544
- `transfer.unpackLimit` is used instead.
1545
-
1546
-fetch.prune::
1547
- If true, fetch will automatically behave as if the `--prune`
1548
- option was given on the command line. See also `remote.<name>.prune`
1549
- and the PRUNING section of linkgit:git-fetch[1].
1550
-
1551
-fetch.pruneTags::
1552
- If true, fetch will automatically behave as if the
1553
- `refs/tags/*:refs/tags/*` refspec was provided when pruning,
1554
- if not set already. This allows for setting both this option
1555
- and `fetch.prune` to maintain a 1=1 mapping to upstream
1556
- refs. See also `remote.<name>.pruneTags` and the PRUNING
1557
- section of linkgit:git-fetch[1].
1558
-
1559
-fetch.output::
1560
- Control how ref update status is printed. Valid values are
1561
- `full` and `compact`. Default value is `full`. See section
1562
- OUTPUT in linkgit:git-fetch[1] for detail.
1563
-
1564
-fetch.negotiationAlgorithm::
1565
- Control how information about the commits in the local repository is
1566
- sent when negotiating the contents of the packfile to be sent by the
1567
- server. Set to "skipping" to use an algorithm that skips commits in an
1568
- effort to converge faster, but may result in a larger-than-necessary
1569
- packfile; The default is "default" which instructs Git to use the default algorithm
1570
- that never skips commits (unless the server has acknowledged it or one
1571
- of its descendants).
1572
- Unknown values will cause 'git fetch' to error out.
1573
-+
1574
-See also the `--negotiation-tip` option for linkgit:git-fetch[1].
1510
+include::fetch-config.txt[]
1511
1512
format.attach::
1513
Enable multipart/mixed attachments as the default for
Documentation/fetch-config.txt
new
+65
@@ -0,0 +1,65 @@
1
+fetch.recurseSubmodules::
2
+ This option can be either set to a boolean value or to 'on-demand'.
3
+ Setting it to a boolean changes the behavior of fetch and pull to
4
+ unconditionally recurse into submodules when set to true or to not
5
+ recurse at all when set to false. When set to 'on-demand' (the default
6
+ value), fetch and pull will only recurse into a populated submodule
7
+ when its superproject retrieves a commit that updates the submodule's
8
+ reference.
9
+
10
+fetch.fsckObjects::
11
+ If it is set to true, git-fetch-pack will check all fetched
12
+ objects. See `transfer.fsckObjects` for what's
13
+ checked. Defaults to false. If not set, the value of
14
+ `transfer.fsckObjects` is used instead.
15
+
16
+fetch.fsck.<msg-id>::
17
+ Acts like `fsck.<msg-id>`, but is used by
18
+ linkgit:git-fetch-pack[1] instead of linkgit:git-fsck[1]. See
19
+ the `fsck.<msg-id>` documentation for details.
20
+
21
+fetch.fsck.skipList::
22
+ Acts like `fsck.skipList`, but is used by
23
+ linkgit:git-fetch-pack[1] instead of linkgit:git-fsck[1]. See
24
+ the `fsck.skipList` documentation for details.
25
+
26
+fetch.unpackLimit::
27
+ If the number of objects fetched over the Git native
28
+ transfer is below this
29
+ limit, then the objects will be unpacked into loose object
30
+ files. However if the number of received objects equals or
31
+ exceeds this limit then the received pack will be stored as
32
+ a pack, after adding any missing delta bases. Storing the
33
+ pack from a push can make the push operation complete faster,
34
+ especially on slow filesystems. If not set, the value of
35
+ `transfer.unpackLimit` is used instead.
36
+
37
+fetch.prune::
38
+ If true, fetch will automatically behave as if the `--prune`
39
+ option was given on the command line. See also `remote.<name>.prune`
40
+ and the PRUNING section of linkgit:git-fetch[1].
41
+
42
+fetch.pruneTags::
43
+ If true, fetch will automatically behave as if the
44
+ `refs/tags/*:refs/tags/*` refspec was provided when pruning,
45
+ if not set already. This allows for setting both this option
46
+ and `fetch.prune` to maintain a 1=1 mapping to upstream
47
+ refs. See also `remote.<name>.pruneTags` and the PRUNING
48
+ section of linkgit:git-fetch[1].
49
+
50
+fetch.output::
51
+ Control how ref update status is printed. Valid values are
52
+ `full` and `compact`. Default value is `full`. See section
53
+ OUTPUT in linkgit:git-fetch[1] for detail.
54
+
55
+fetch.negotiationAlgorithm::
56
+ Control how information about the commits in the local repository is
57
+ sent when negotiating the contents of the packfile to be sent by the
58
+ server. Set to "skipping" to use an algorithm that skips commits in an
59
+ effort to converge faster, but may result in a larger-than-necessary
60
+ packfile; The default is "default" which instructs Git to use the default algorithm
61
+ that never skips commits (unless the server has acknowledged it or one
62
+ of its descendants).
63
+ Unknown values will cause 'git fetch' to error out.
64
++
65
+See also the `--negotiation-tip` option for linkgit:git-fetch[1].