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

Re: [PATCH] remote.c - Make remote definition require a url

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 13, 2014, 17:19 UTC
Message-ID
<xmqqppdv51lv.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1413040849-20056-1-git-send-email-mlevedahl@gmail.com>
Mark Levedahl <mlevedahl@gmail.com> writes:
> Some options may be configured globally for a remote (e.g, tagopt).

Or some remotes may have only pushurl and not url. "git remote" output for me has a few such remotes but wouldn't this patch break it?

If a caller that walks the list of remotes misbehaves only because it assumes that r->url always is always valid, isn't that assumption what needs to be fixed? for_each_remote() should be kept as a way to enumerate all the [remote "foo"], I would think.

Previous: Mark LevedahlNext: Mark Levedahl
Message 2 of 3 in “remote.c - Make remote definition require a url”
  1. remote.c - Make remote definition require a urlMark Levedahl, Oct 11, 2014
  2. Junio C HamanoOct 13, 2014
  3. Mark LevedahlOct 14, 2014

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.