Dale Rowley <ddrowley3 <at> juno.com> writes: > git config --unset branch.master.remote > git push Yes, those 2 commands don't make much sense. I should have mentioned that this was just the simplest way to reproduce the problem. My original and more realistic scenario: git clone /path/to/some/repo cd repo git remote add remote1 <url> git remote add remote2 <url> git config --unset branch.master.remote git push remote1 (seg fault) The reason for unsetting branch.master.remote was to force git to complain and abort if I accidentally typed 'git push' instead of 'git push <remote>' (I wanted to avoid accidentally pushing to the wrong remote repo). Dale -- 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