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

Re: [PATCH] Give error when no remote is configured

From
Bernie Innocenti <bernie@codewiz.org>
Date
Mar 11, 2009, 06:19 UTC
Message-ID
<49B757E3.8000807@codewiz.org>
In-Reply-To
<alpine.LNX.1.00.0903110139450.19665@iabervon.org>
Daniel Barkalow wrote:
Show 5 quoted lines
> When there's no explicitly-named remote, we use the remote specified
> for the current branch, which in turn defaults to "origin". But it
> this case should require the remote to actually be configured, and not
> fall back to the path "origin".
> [...]
Thanks, works like a charm!
-- 
   // Bernie Innocenti - http://www.codewiz.org/
 \X/  Sugar Labs       - http://www.sugarlabs.org/
Previous: Daniel BarkalowNext: Junio C Hamano
Message 2 of 7 in “Give error when no remote is configured”
  1. Give error when no remote is configuredDaniel Barkalow, Mar 11, 2009
  2. Bernie InnocentiMar 11, 2009
  3. Junio C HamanoMar 16, 2009
  4. Daniel BarkalowMar 16, 2009
  5. Jay SoffianMar 16, 2009
  6. Giovanni BajoMar 17, 2009
  7. Daniel BarkalowMar 17, 2009

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.