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, 21:44 UTC
Message-ID
<xmqqwog0tt27.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20190729192040.GD14943@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> Yeah, the auto-update of the tracking refs came later (so I think you
> could argue the bad interaction is my fault!).
Heh, I somehow thought it was somebody else.
> Hmm, true. I'd almost argue that --force-with-lease, at least in its
> default mode with no explicit lease source specified, should allow an
> update from X to Y to be a successful noop if the remote "somehow"
> already moved to Y.

I've already written the --force-with-lease that expects what you have on your remote-tracking branch off as a gross misdesign that should be deprecated in the longer term; I do not have a strong opinion on the tweaks to be done to the feature until it gets dropped ;-)

Previous: Jeff KingNext: Jeff King
Message 11 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.