From: Jakub Narebski <jnareb@gmail.com>
To: Pierre Habouzit <madcoder@debian.org>
Cc: Git ML <git@vger.kernel.org>
Subject: Re: THREADED_DELTA_SEARCH
Date: Thu, 10 Jul 2008 01:51:06 -0700 (PDT) [thread overview]
Message-ID: <m3hcaydswg.fsf@localhost.localdomain> (raw)
In-Reply-To: <20080710075327.GD24819@artemis.madism.org>
Pierre Habouzit <madcoder@debian.org> writes:
> I'm using it in production for quite a long time now, and I wonder if
> there is any specific reason why it's not default. Debian activated it
> by default too a couple of weeks ago, which means that it's in
> production on quite a large scale, and there are no issues reported
> either. Would a patch making it default be accepted ? It's quite handy
> given that SMP machines are really pervasive nowadays…
Doues our ./configure detects if it makes sense (i.e. if it is SMP
machine)? What is the cost of THREADED_DELTA_SEARCH for single processor
single core machine?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-07-10 8:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 7:53 THREADED_DELTA_SEARCH Pierre Habouzit
2008-07-10 8:01 ` THREADED_DELTA_SEARCH Johannes Sixt
2008-07-10 16:50 ` THREADED_DELTA_SEARCH Andreas Ericsson
2008-07-10 8:51 ` Jakub Narebski [this message]
2008-07-10 9:33 ` THREADED_DELTA_SEARCH Pierre Habouzit
2008-07-10 15:34 ` THREADED_DELTA_SEARCH Junio C Hamano
2008-07-10 16:21 ` THREADED_DELTA_SEARCH Nicolas Pitre
2008-07-10 20:13 ` THREADED_DELTA_SEARCH Alex Riesen
2008-07-10 20:26 ` THREADED_DELTA_SEARCH Nicolas Pitre
2008-07-10 20:29 ` THREADED_DELTA_SEARCH Alex Riesen
2008-07-10 20:36 ` THREADED_DELTA_SEARCH Nicolas Pitre
2008-07-10 22:19 ` THREADED_DELTA_SEARCH Alex Riesen
[not found] ` <alpine.DEB.1.00.0807110032030.3279@eeepc-johanness>
[not found] ` <alpine.LFD.1.10.0807101851520.12484@xanadu.home>
[not found] ` <81b0412b0807102259q1046051bwc513eadb50847675@mail.gmail.com>
2008-07-11 7:41 ` THREADED_DELTA_SEARCH Pierre Habouzit
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=m3hcaydswg.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=madcoder@debian.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).