git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dov Grobgeld <dov.grobgeld@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael Witten <mfwitten@gmail.com>, git@vger.kernel.org
Subject: Re: Why do some commits not appear in "git log"?
Date: Sat, 6 Aug 2011 20:43:59 +0300	[thread overview]
Message-ID: <CA++fsGE2JfnHc2JCsJg21FLXGfMWnzCjpUdwk+dcK72e5P18eg@mail.gmail.com> (raw)
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:
>
> 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.

      parent reply	other threads:[~2011-08-06 17:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA++fsGGG7pLt4xoeJozGnYEwOrs6NuzStYPKF_L5k49uzFB-4A@mail.gmail.com>
2011-08-02 15:38 ` Why do some commits not appear in "git log"? Dov Grobgeld
2011-08-02 15:56   ` Michael Witten
2011-08-03  5:47     ` Dov Grobgeld
2011-08-03 18:57       ` Junio C Hamano
     [not found]         ` <CA++fsGG1xHm2ubXB-EL56L6xSau9AQX=o8fvmZb_7zNFkqdW2w@mail.gmail.com>
2011-08-06 17:43           ` Dov Grobgeld [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA++fsGE2JfnHc2JCsJg21FLXGfMWnzCjpUdwk+dcK72e5P18eg@mail.gmail.com \
    --to=dov.grobgeld@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mfwitten@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).