[PATCH 0/5] Allow push and fetch urls to be different

This series implements a new config setting remote.${remotename}.pushurl which allows the urls for fetch and push to be different.

In http://permalink.gmane.org/gmane.comp.version-control.git/120726 the feature was suggested, and an initital WIP/RFC was discussed. The patch 1/5 contains exactly that version amended with documentation.

If there is no pushurl then all values of remote.${remotename}.url are used for pushes just like before. Otherwise, all values of remote.${remotename}.pushurl are used for pushes. In any case, the first value of remote.${remotename}.url is used for fetches.

1/5 implements the config setting, makes push obey it and documents it. 2/5 adds tests for the new setting. 3/5 updates the api doc. 4/5 makes "remote show ${remotename}" show the new push URLs, and makes clear which ones are used for fetch and which ones for push. 5/5 brings the output of "remote -v" more in line with the output of the above (it was out of sync even before 4/5).

1 through 3 apply on yesterday's next.

4 through 5 require tomorrow's next ;) More specifically, 4 requires 'builtin-remote: Make "remote show" display all urls' which I suggested for applying to maint in http://permalink.gmane.org/gmane.comp.version-control.git/120924 because I think the current output is incomplete. If that patch is not considered for separate inclusion in maint or master I would suggest squashing it together with 4/5 of the above.

Michael J Gruber (5):
  Allow push and fetch urls to be different
  t5516: Check pushurl config setting
  technical/api-remote: Describe new struct remote member pushurl
  builtin-remote: Show push urls as well
  builtin-remote: Make "remote -v" display push urls