Re: [BUG?] git log picks up bad commit
- From
Jeff King <peff@peff.net>
- Date
- Feb 3, 2008, 03:00 UTC
- Message-ID
- <20080203030054.GA18654@coredump.intra.peff.net>
- In-Reply-To
- <20080202122135.GA5783@code-monkey.de>
On Sat, Feb 02, 2008 at 01:21:36PM +0100, Tilman Sauerbeck wrote:
> I think I either found a bug in git log, or I'm working with a broken > repository. I can reproduce this with current git master.
I think it is a bug in your command line.
> git log -n 3 --abbrev-commit --pretty=oneline \ > 1dd567d596b072e3ce44ea5ad8c373871686b078.. 2.4
The space betwen ".." and "2.4" means that they are two separate arguments. Thus the second part of your ".." operator is blank, which is treated as HEAD. Thus it is equivalent to:
1dd567d596b072e3ce44ea5ad8c373871686b078..HEAD 2.4
When you switch to branch 2.4, then 2.4 becomes your HEAD.
That being said, the commit in your 'master' branch _is_ part of 1dd567d5, and should be culled. So I'm not clear on why it shows up only when you ask to see both branches, and that may be a bug.
-Peff