git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-push segfault

From
DRDale Rowley <ddrowley3@juno.com>
Date
Feb 24, 2010, 06:02 UTC
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
Previous: Dale RowleyNext: Jeff King
Message 2 of 6 in “git-push segfault”
  1. Dale RowleyFeb 24, 2010
  2. Dale RowleyFeb 24, 2010
  3. Jeff KingFeb 24, 2010
  4. Andreas KreyFeb 24, 2010
  5. Jeff KingFeb 24, 2010
  6. Andreas KreyFeb 24, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.