Git fork

config: document remote.*.url/pushurl interaction

The documentation for these keys gives a very terse definition and
points you to the fetch/push manpages. But from reading those pages it
was not at all obvious to me that:

- these are keys that can be defined multiple times with meaningful
behavior (especially remote.*.url)

- the way that pushurl overrides url (the git-push page does mention
that "pushurl defaults to url", but it is not immediately clear what
a multi-valued url would do in that situation).

Let's try to summarize the current behavior.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>

authored by

Jeff King and committed by
Junio C Hamano
bd1b88dc b68118d2

+7 -1
+7 -1
Documentation/config/remote.txt
··· 5 5 6 6 remote.<name>.url:: 7 7 The URL of a remote repository. See linkgit:git-fetch[1] or 8 - linkgit:git-push[1]. 8 + linkgit:git-push[1]. A configured remote can have multiple URLs; 9 + in this case the first is used for fetching, and all are used 10 + for pushing (assuming no `remote.<name>.pushurl` is defined). 9 11 10 12 remote.<name>.pushurl:: 11 13 The push URL of a remote repository. See linkgit:git-push[1]. 14 + If a `pushurl` option is present in a configured remote, it 15 + is used for pushing instead of `remote.<name>.url`. A configured 16 + remote can have multiple push URLs; in this case a push goes to 17 + all of them. 12 18 13 19 remote.<name>.proxy:: 14 20 For remotes that require curl (http, https and ftp), the URL to