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

Re: [PATCH 1/3] git remote update: Report error for non-existing groups

From
Jeff King <peff@peff.net>
Date
Apr 8, 2009, 17:08 UTC
Message-ID
<20090408170844.GB28069@coredump.intra.peff.net>
In-Reply-To
<7vy6ubo8tn.fsf@gitster.siamese.dyndns.org>
On Wed, Apr 08, 2009 at 01:20:36AM -0700, Junio C Hamano wrote:
> I don't know what users want to see when they say "default" explicitly
> without having an explicit configuration.  Should it do the same thing as
> "git remote update"?

I'm not sure we have a choice anymore; is it worth breaking compatibility to "fix" something that doesn't actually seem to be harming anyone?

-Peff
Previous: Junio C HamanoNext: Junio C Hamano
Message 6 of 10 in “git remote update: Check args and fallback to remotes”
  1. 0/3 git remote update: Check args and fallback to remotesFinn Arne Gangstad, Apr 6, 2009
  2. 1/3 git remote update: Report error for non-existing groupsFinn Arne Gangstad, Apr 6, 2009
  3. Junio C HamanoApr 8, 2009
  4. Finn Arne GangstadApr 8, 2009
  5. Junio C HamanoApr 8, 2009
  6. Jeff KingApr 8, 2009
  7. Junio C HamanoApr 8, 2009
  8. 2/3 remote: New function remote_is_configured()Finn Arne Gangstad, Apr 6, 2009
  9. 3/3 git remote update: Fallback to remote if group does not existFinn Arne Gangstad, Apr 6, 2009
  10. Jeff KingApr 6, 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.