From: Dale Rowley <ddrowley3@juno.com>
Date: Wed, 24 Feb 2010 06:02:59 GMT
Subject: Re: git-push segfault
Message-ID: <loom.20100224T062506-877@post.gmane.org>
In-Reply-To: <loom.20100224T043557-954@post.gmane.org>

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