All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Seymour <jon.seymour@gmail.com>
To: gitzilla@gmail.com
Cc: Linus Torvalds <torvalds@osdl.org>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: git-rev-list --merge-order bug?
Date: Thu, 30 Jun 2005 08:40:16 +1000	[thread overview]
Message-ID: <2cfc403205062915406db3a03@mail.gmail.com> (raw)
In-Reply-To: <42C2F30A.7030102@gmail.com>

> 
> 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/

      reply	other threads:[~2005-06-29 22:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29 19:14 git-rev-list --merge-order bug? A Large Angry SCM
2005-06-29 22:40 ` Jon Seymour [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=2cfc403205062915406db3a03@mail.gmail.com \
    --to=jon.seymour@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitzilla@gmail.com \
    --cc=jon@blackcubes.dyndns.org \
    --cc=torvalds@osdl.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.