config.txt: move checkout.* 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>
This commit is contained in:
parent
6b0b974060
commit
9140b410d2
@ -305,29 +305,7 @@ include::config/branch.txt[]
|
|||||||
|
|
||||||
include::config/browser.txt[]
|
include::config/browser.txt[]
|
||||||
|
|
||||||
checkout.defaultRemote::
|
include::config/checkout.txt[]
|
||||||
When you run 'git checkout <something>' and only have one
|
|
||||||
remote, it may implicitly fall back on checking out and
|
|
||||||
tracking e.g. 'origin/<something>'. This stops working as soon
|
|
||||||
as you have more than one remote with a '<something>'
|
|
||||||
reference. This setting allows for setting the name of a
|
|
||||||
preferred remote that should always win when it comes to
|
|
||||||
disambiguation. The typical use-case is to set this to
|
|
||||||
`origin`.
|
|
||||||
+
|
|
||||||
Currently this is used by linkgit:git-checkout[1] when 'git checkout
|
|
||||||
<something>' will checkout the '<something>' branch on another remote,
|
|
||||||
and by linkgit:git-worktree[1] when 'git worktree add' refers to a
|
|
||||||
remote branch. This setting might be used for other checkout-like
|
|
||||||
commands or functionality in the future.
|
|
||||||
|
|
||||||
checkout.optimizeNewBranch::
|
|
||||||
Optimizes the performance of "git checkout -b <new_branch>" when
|
|
||||||
using sparse-checkout. When set to true, git will not update the
|
|
||||||
repo based on the current sparse-checkout settings. This means it
|
|
||||||
will not update the skip-worktree bit in the index nor add/remove
|
|
||||||
files in the working directory to reflect the current sparse checkout
|
|
||||||
settings nor will it show the local changes.
|
|
||||||
|
|
||||||
clean.requireForce::
|
clean.requireForce::
|
||||||
A boolean to make git-clean do nothing unless given -f,
|
A boolean to make git-clean do nothing unless given -f,
|
||||||
|
23
Documentation/config/checkout.txt
Normal file
23
Documentation/config/checkout.txt
Normal file
@ -0,0 +1,23 @@
|
|||||||
|
checkout.defaultRemote::
|
||||||
|
When you run 'git checkout <something>' and only have one
|
||||||
|
remote, it may implicitly fall back on checking out and
|
||||||
|
tracking e.g. 'origin/<something>'. This stops working as soon
|
||||||
|
as you have more than one remote with a '<something>'
|
||||||
|
reference. This setting allows for setting the name of a
|
||||||
|
preferred remote that should always win when it comes to
|
||||||
|
disambiguation. The typical use-case is to set this to
|
||||||
|
`origin`.
|
||||||
|
+
|
||||||
|
Currently this is used by linkgit:git-checkout[1] when 'git checkout
|
||||||
|
<something>' will checkout the '<something>' branch on another remote,
|
||||||
|
and by linkgit:git-worktree[1] when 'git worktree add' refers to a
|
||||||
|
remote branch. This setting might be used for other checkout-like
|
||||||
|
commands or functionality in the future.
|
||||||
|
|
||||||
|
checkout.optimizeNewBranch::
|
||||||
|
Optimizes the performance of "git checkout -b <new_branch>" when
|
||||||
|
using sparse-checkout. When set to true, git will not update the
|
||||||
|
repo based on the current sparse-checkout settings. This means it
|
||||||
|
will not update the skip-worktree bit in the index nor add/remove
|
||||||
|
files in the working directory to reflect the current sparse checkout
|
||||||
|
settings nor will it show the local changes.
|
Loading…
Reference in New Issue
Block a user