[PATCH] doc: clarify "explicitly given" in push.default
- From
Bert Wesarg <bert.wesarg@googlemail.com>
- Date
- Jan 27, 2020, 09:25 UTC
- Message-ID
- <1113893dd36a1e8cf72331dd01f36206b44f45ad.1580116685.git.bert.wesarg@googlemail.com>
- In-Reply-To
- <20200127070238.GA32427@coredump.intra.peff.net>
The documentation for push.default mentions that it is used if no refspec is "explicitly given". Let's clarify that giving a refspec on the command-line _or_ in the config will override it.
Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Bert Wesarg <bert.wesarg@googlemail.com> --- Documentation/config/push.txt | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-)
Cc: peff@peff.net
diff --git a/Documentation/config/push.txt b/Documentation/config/push.txt index 0a0e000569..d560362c9a 100644 --- a/Documentation/config/push.txt +++ b/Documentation/config/push.txt @@ -1,9 +1,11 @@ push.default:: Defines the action `git push` should take if no refspec is - explicitly given. 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: + neither explicitly (on the command-line) nor implicitly (via a + `remote.*.push` config option) given. 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: + --
-- 2.24.1.497.g9abd7b20b4.dirty