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

Re: Push force-with-lease with multi-URL remote

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 29, 2019, 13:33 UTC
Message-ID
<xmqq7e81vuc3.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20190729102009.GC2755@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> My general feeling is that having multiple push URLs for a remote is a
> poorly designed feature in Git (and I think the discussion elsewhere in
> this thread went there, as well).

That's being generous. I do not think it was even designed---at least, the interaction with remote-tracking is ill thought out, but I think the updating of remote-tracking by pretending to have turned around and fetched immediately after it has done its thing came much later than multiple URLs for push. A remote with multiple URLs without any remote-tracking (i.e. "push only remote") behaves semi-sensibly.

> But since we do have it, and if we are not going to deprecate it[1], it
> seems like this case should pick the X value of myremote/mybranch ahead
> of time, and then use it consistently for each push.

I agree but only if the listed ones are separate ones. If the URLs are separate paths to reach the same remote (e.g. https:// and ssh:// going to the same place), the current definition would make more sense.

Previous: Jeff KingNext: Christopher Head
Message 8 of 12 in “Push force-with-lease with multi-URL remote”
  1. Christopher HeadJul 27, 2019
  2. Junio C HamanoJul 27, 2019
  3. Christopher HeadJul 27, 2019
  4. Junio C HamanoJul 27, 2019
  5. Christopher HeadJul 27, 2019
  6. Junio C HamanoJul 29, 2019
  7. Jeff KingJul 29, 2019
  8. Junio C HamanoJul 29, 2019
  9. Christopher HeadJul 29, 2019
  10. Jeff KingJul 29, 2019
  11. Junio C HamanoJul 29, 2019
  12. Jeff KingJul 29, 2019

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.