Hello guys, I'm replying a bit late, had much to work in the last days. I really like some ideas discussed here and want to state that - "git push" without options is much easier and does nothing wrong, if you configured the branch.$name.pushto correctly - I also think that having support for multiple push destinations per branch would be excellent for a distributed version control system like git - doing 'git push origin master:myremote/myname' just covers to much redundant data, which imho can (but not must) be put into .git/config - I don't care about the configuration names, we can even stick to "merge" for now and add simply add "push" and rename them in git 2.x I currently would like this variant mostly, allowing high flexibility: -------------------------------------------------------------------------------- [remote "myremote"] url = git+ssh://.... # no change ref = refs/heads/ # renamed fetch = ... # that way we can use the remote for fetch and push: [branch "master"] merge = myremote push = myremote push = anotherremote [branch "otherbranch"] merge = otherremote push = otherremote push = classmate push = myremote -------------------------------------------------------------------------------- What do you think about that approach? Sincerly Nico -- Think about Free and Open Source Software (FOSS). http://nico.schottelius.org/documentations/foss/the-term-foss/ PGP: BFE4 C736 ABE5 406F 8F42 F7CF B8BE F92A 9885 188C
Attachment:
signature.asc
Description: Digital signature
