Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: A Large Angry SCM <gitzilla@gmail.com>, git@vger.kernel.org
Subject: Re: merge-base: update the clean-up postprocessing
Date: Wed, 05 Jul 2006 16:20:15 -0700	[thread overview]
Message-ID: <7v4pxvbpw0.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0607050946390.29667@wbgn013.biozentrum.uni-wuerzburg.de> (Johannes Schindelin's message of "Wed, 5 Jul 2006 09:50:53 +0200 (CEST)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> On Tue, 4 Jul 2006, Junio C Hamano wrote:
>
>> This is "for concepts" only -- it still seems to have bugs
>> somewhere to break other tests, although it passes your new
>> tests.
>
> Doesn't this introduce a nasty O(n*m) performance (where m is the 
> number of merge bases, and n the number of traversed commits)? I think 
> possibly many commits are traversed multiple times.

In practice m is small and the recomputation of bases between
bases does not require the minimalization so O(m^2).  I've given
the numbers from a small real world example on the fixed code.

  reply	other threads:[~2006-07-05 23:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-05  0:35 [PATCH] Additional merge-base tests (revised) A Large Angry SCM
2006-07-05  2:07 ` merge-base: update the clean-up postprocessing Junio C Hamano
2006-07-05  7:50   ` Johannes Schindelin
2006-07-05 23:20     ` Junio C Hamano [this message]
2006-07-05 23:21     ` Junio C Hamano
2006-07-05  7:51   ` Junio C Hamano
2006-07-11  8:13     ` Junio C Hamano
2006-07-11 14:26       ` Johannes Schindelin

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=7v4pxvbpw0.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitzilla@gmail.com \
    /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