Re: git-rev-list --merge-order bug?

From: Jon Seymour <jon.seymour@gmail.com>
Date: Jun 29, 2005, 22:40 UTC
Message-ID: <2cfc403205062915406db3a03@mail.gmail.com>
In-Reply-To: <42C2F30A.7030102@gmail.com>

Show 9 quoted lines

> 
> git-rev-list ee28152d03f2cf4b5e3ebc25f7f03f9654d3aa0d \
>         ^aa03413467a2f2ada900817dc2a8e3904549b5fe |wc -l
> 
> git-rev-list ee28152d03f2cf4b5e3ebc25f7f03f9654d3aa0d \
>         ^aa03413467a2f2ada900817dc2a8e3904549b5fe --merge-order |wc -l
> 
> The first git-rev-list returns 4 commits and the second returns 304.
>

I'll look at it.

It appears to do in cases that look like this:

A
|   B
|   |
|  /
C

git-rev-list B ^A --merge-order

jon.

-- 
homepage: http://www.zeta.org.au/~jon/
blog: http://orwelliantremors.blogspot.com/