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

Re: Why do some commits not appear in "git log"?

From
Dov Grobgeld <dov.grobgeld@gmail.com>
Date
Aug 6, 2011, 17:43 UTC
Message-ID
<CA++fsGE2JfnHc2JCsJg21FLXGfMWnzCjpUdwk+dcK72e5P18eg@mail.gmail.com>
In-Reply-To
<CA++fsGG1xHm2ubXB-EL56L6xSau9AQX=o8fvmZb_7zNFkqdW2w@mail.gmail.com>

Ok, now I grok it. Indeed these "substantial changes" by mistake undid another large change. So the net result was zero, which git was smart enough to figure out, and therefore these two changes +D and -D cancelled one another and none of them were shown.

Thanks a lot! Dov

On Wed, Aug 3, 2011 at 21:57, Junio C Hamano <gitster@pobox.com> wrote:
Show 13 quoted lines
>
> Dov Grobgeld <dov.grobgeld@gmail.com> writes:
>
> > --full-history indeed made the missing commits show up! So why was the
> > commit pruned? It contains some substantial source changes...
>
> I suspect that these "substantial changes" did not make any contribution
> to the end result. Read
>
> http://thread.gmane.org/gmane.comp.version-control.git/89400/focus=90659
>
> These days, the --post-simplify option implemented in that discussion
> thread is called --simplify-merges or something, I think.
Previous: Junio C Hamano
Message 5 of 5 in “Why do some commits not appear in "git log"?”
  1. Dov GrobgeldAug 2, 2011
  2. Michael WittenAug 2, 2011
  3. Dov GrobgeldAug 3, 2011
  4. Junio C HamanoAug 3, 2011
  5. Dov GrobgeldAug 6, 2011

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.