From: Jon Seymour <jon.seymour@gmail.com>
To: Radoslaw Szkodzinski <astralstorm@gorzow.mm.pl>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-rev-list --merge-order hangs
Date: Thu, 9 Jun 2005 00:17:27 +1000 [thread overview]
Message-ID: <2cfc40320506080717585bf939@mail.gmail.com> (raw)
In-Reply-To: <2cfc4032050608020215152887@mail.gmail.com>
Ok, I reproduced exponential behaviour when a commit with no parents
is merged near the head of the kernel and a ^ argument is specified.
Fortunately a work-around is a one line change - a patch will be
forthcoming shortly.
The workaround will still require a full-graph scan but that is linear
rather than
exponential so is tolerable.
A better solution which will not require a full-graph scan will be
delivered in a future
patch.
Thanks for the report.
jon.
next prev parent reply other threads:[~2005-06-09 4:42 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
[not found] ` <2cfc403205060800337e1ecca0@mail.gmail.com>
2005-06-08 9:02 ` Jon Seymour
2005-06-08 14:17 ` Jon Seymour [this message]
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=2cfc40320506080717585bf939@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).