doc: drop "explicitly given" from push.default description
The documentation for push.default mentions that it is used if no refspec is "explicitly given". Let's drop the notion of "explicit" here, since it's vague, and just mention that any refspec from anywhere is sufficient to override this. I've dropped the mention of "explicitly given" from the definition of the "nothing" value right below, too. It's close enough to our clarification that it should be obvious we mean the same type of "given" here. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jeff King committed
Jan 29, 2020 at 00:53 UTC
8b2a1928f08a0c795de1a84aa329bc85dcdb3949
1 file changed
+3
-2
Documentation/config/push.txt
+3
-2
@@ -1,6 +1,7 @@
1
push.default::
2
Defines the action `git push` should take if no refspec is
3
- explicitly given. Different values are well-suited for
3
+ given (whether from the command-line, config, or elsewhere).
4
+ Different values are well-suited for
5
specific workflows; for instance, in a purely central workflow
6
(i.e. the fetch source is equal to the push destination),
7
`upstream` is probably what you want. Possible values are:
@@ -8,7 +9,7 @@ push.default::
9
--
10
11
* `nothing` - do not push anything (error out) unless a refspec is
11
- explicitly given. This is primarily meant for people who want to
12
+ given. This is primarily meant for people who want to
13
avoid mistakes by always being explicit.
14
15
* `current` - push the current branch to update a branch with the same