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

Re: Work is not replayed on top while: git pull -v --rebase

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 20, 2018, 14:38 UTC
Message-ID
<xmqq36u42pzw.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<6160201537441514@iva5-cb9df376e345.qloud-c.yandex.net>
KES <kes-kes@yandex.ru> writes:
> PS. for `git push --force` there is alternative: --force-with-lease
> Is there something similar to --force-with-lease but for `git pull -v --rebase`?
Curious.

For "push", you are competing with the other pushers who want to update the repository over there, and there is need for the force-with-lease=<it must be this verison> safety, but what is the reason why you need to take a lease on your local side while doing a "pull"?

Previous: KESNext: KES
Message 2 of 4 in “Work is not replayed on top while: git pull -v --rebase”
  1. KESSep 20, 2018
  2. Junio C HamanoSep 20, 2018
  3. KESSep 25, 2018
  4. KESSep 25, 2018

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.