git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Seymour <jon.seymour@gmail.com>
To: Radoslaw Szkodzinski <astralstorm@gorzow.mm.pl>
Cc: git@vger.kernel.org
Subject: Re: git-rev-list --merge-order hangs
Date: Wed, 8 Jun 2005 17:22:04 +1000	[thread overview]
Message-ID: <2cfc4032050608002258e58897@mail.gmail.com> (raw)
In-Reply-To: <42A69550.1030105@gorzow.mm.pl>

On 6/8/05, Radoslaw Szkodzinski <astralstorm@gorzow.mm.pl> wrote:
> I've got a Linux git tree with some merges and some other commits
> interwined.
> I want to print all my changes in merge order, so I do:
> 
> git-rev-list --pretty --merge-order v2.6.12-rc6-astorm1 ^v2.6.12-rc6
> 
> It prints the first 3 commits (linear), but then hangs, eating all
> available CPU.
> Without --merge-order it works fine, but obviously lists the commits by
> parent.

Can you git-rev-list >/dev/null without arguments, then do a
git-rev-list --pretty --merge-order again and see it works any better?

If it still doesn't work, can you send me the output of:

        git-rev-list --parents v2.6.12-rc6-astorm1 ^v2.6.12-rc6 

I may then need to request a tarball of the related git objects so
that I can reproduce the problem on my end, but I'll send you the list
I need to see.

Regards,

jon.

  reply	other threads:[~2005-06-08  7:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08  6:50 git-rev-list --merge-order hangs Radoslaw Szkodzinski
2005-06-08  7:22 ` Jon Seymour [this message]
     [not found]   ` <2cfc403205060800337e1ecca0@mail.gmail.com>
2005-06-08  9:02     ` Jon Seymour
2005-06-08 14:17       ` Jon Seymour
2005-06-08 15:28       ` Radoslaw Szkodzinski

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=2cfc4032050608002258e58897@mail.gmail.com \
    --to=jon.seymour@gmail.com \
    --cc=astralstorm@gorzow.mm.pl \
    --cc=git@vger.kernel.org \
    --cc=jon@blackcubes.dyndns.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 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).