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

Re: How to view diff when doing `git push --force`

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Mar 11, 2017, 19:30 UTC
Message-ID
<CACBZZX5g95nTtA5--g8K29FjQ=dU3JLEfVXZjUs8J2Y-QCzYHg@mail.gmail.com>
In-Reply-To
<6962041489243945@web20g.yandex.ru>
On Sat, Mar 11, 2017 at 3:52 PM, KES <kes-kes@yandex.ru> wrote:
Show 18 quoted lines
> Hi. I have done `git push --force` but I forget to `pull`,
>
> Counting objects: 7, done.
> Delta compression using up to 4 threads.
> Compressing objects: 100% (7/7), done.
> Writing objects: 100% (7/7), 765 bytes | 0 bytes/s, done.
> Total 7 (delta 6), reused 0 (delta 0)
> To xxxgit:cry/cry.git
>  + 48e9058...117ee39 staging -> staging (forced update)
>
> But I can not view diff:
>
> git show 48e9058...117ee39
> fatal: ambiguous argument '48e9058...117ee39': unknown revision or path not in the working tree.
> Use '--' to separate paths from revisions, like this:
> 'git <command> [<revision>...] -- [<file>...]'
>
> May I pull info about changes that was deleted?

At this point, no, but in the future instead of --force use --force-with-lease=<refname>:<expect> where <expect> is e.g. $(git rev-parse HEAD).

Previous: KESNext: KES
Message 2 of 3 in “How to view diff when doing `git push --force`”
  1. KESMar 11, 2017
  2. Ævar Arnfjörð BjarmasonMar 11, 2017
  3. KESJan 10, 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.