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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 3, 2011, 18:57 UTC
Message-ID
<7vipqeb9wg.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CA++fsGGhzVkXTPLui+DfTFcjve7w80Kud4RxC0p=5AenOcBSDw@mail.gmail.com>
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: Dov GrobgeldNext: Dov Grobgeld
Message 4 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.