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
KKES <kes-kes@yandex.ru>
Date
Sep 25, 2018, 06:42 UTC
Message-ID
<21782811537857740@sas2-857317bd6599.qloud-c.yandex.net>
In-Reply-To
<xmqq36u42pzw.fsf@gitster-ct.c.googlers.com>
As you can see I have lost some commits. Thus I wanna an option to be safe
20.09.2018, 17:38, "Junio C Hamano" <gitster@pobox.com>:
Show 12 quoted lines
> 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: Junio C HamanoNext: KES
Message 3 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.