From: "Michael S. Tsirkin" <mst@mellanox.co.il>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: git log - filter missing changesets
Date: Thu, 17 Aug 2006 11:58:30 +0300 [thread overview]
Message-ID: <20060817085830.GD2630@mellanox.co.il> (raw)
In-Reply-To: <7v7j17u4zw.fsf@assigned-by-dhcp.cox.net>
Quoting r. Junio C Hamano <junkio@cox.net>:
> Subject: Re: git log - filter missing changesets
>
> "Michael S. Tsirkin" <mst@mellanox.co.il> writes:
>
> > Hi!
> > git log with -- parameter seems to sometimes miss changesets that
> > affect a specific directory:
> > ...
> > what gives?
>
> Most likely history simplification threw away the entire side
> branch.
>
> This is getting to be a FAQ I suspect.
>
> http://thread.gmane.org/gmane.comp.version-control.git/21633
>
>
Yes, --full-history helps. Thanks!
I'm still not sure *when* does this simplification happen -
the changes that got hidden do not add/remove any files - but oh well.
BTW, --full-history does not seem to be documented on git-rev-list(1)
man page.
--
MST
prev parent reply other threads:[~2006-08-17 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 8:25 git log - filter missing changesets Michael S. Tsirkin
2006-08-17 8:43 ` Junio C Hamano
2006-08-17 8:58 ` Michael S. Tsirkin [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=20060817085830.GD2630@mellanox.co.il \
--to=mst@mellanox.co.il \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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