Nico -telmich- Schottelius <nico-linux-git@xxxxxxxxxxxxxxx> writes: > Nice would be > > [branch "master"] > remote-push = origin > remote-push-merge = another_branch > > And thus perhaps also changing the existing specs: > > remote = ... to remote-fetch = ... > merge = ... to remote-fetch-merge = I do not think doing this is worth it, not because I think a single branch.$name.remote should be good enough for everybody, but because once you need a separate remote each for fetching and pushing, there is no reason to say one per direction is enough. An alternative could be to split [remote "name"] url into two variants, fetch-url and push-url. While fetching by default from two places without telling from which one does not make any sense, pushing by default to two different places is quite a normal thing to do, and we already do support more than one url entries in [remote "name"] section used for pushing. If we were to do this, it might also make sense to rename the word 'origin' we use for the default remote name to 'default' or something. People with shared repository workflow would fetch from one repository and push back to the same repository, so the distinction would not matter, but for others who need something like you suggest, the default repository for fetching and pushing are different, and while you may still consider where you fetch from your 'origin', where you push into is not your 'origin' anymore. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
