merge(3p/git): Merge git upstream at v2.26.2
This commit is contained in:
commit
5229c9b232
1006 changed files with 149006 additions and 60819 deletions
|
|
@ -1,6 +1,7 @@
|
|||
push.default::
|
||||
Defines the action `git push` should take if no refspec is
|
||||
explicitly given. Different values are well-suited for
|
||||
given (whether from the command-line, config, or elsewhere).
|
||||
Different values are well-suited for
|
||||
specific workflows; for instance, in a purely central workflow
|
||||
(i.e. the fetch source is equal to the push destination),
|
||||
`upstream` is probably what you want. Possible values are:
|
||||
|
|
@ -8,7 +9,7 @@ push.default::
|
|||
--
|
||||
|
||||
* `nothing` - do not push anything (error out) unless a refspec is
|
||||
explicitly given. This is primarily meant for people who want to
|
||||
given. This is primarily meant for people who want to
|
||||
avoid mistakes by always being explicit.
|
||||
|
||||
* `current` - push the current branch to update a branch with the same
|
||||
|
|
@ -79,7 +80,7 @@ higher priority configuration file (e.g. `.git/config` in a
|
|||
repository) to clear the values inherited from a lower priority
|
||||
configuration files (e.g. `$HOME/.gitconfig`).
|
||||
+
|
||||
--
|
||||
----
|
||||
|
||||
Example:
|
||||
|
||||
|
|
@ -96,7 +97,7 @@ repo/.git/config
|
|||
|
||||
This will result in only b (a and c are cleared).
|
||||
|
||||
--
|
||||
----
|
||||
|
||||
push.recurseSubmodules::
|
||||
Make sure all submodule commits used by the revisions to be pushed
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue