git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Pierre Habouzit <madcoder@debian.org>, Git ML <git@vger.kernel.org>
Subject: Re: THREADED_DELTA_SEARCH
Date: Thu, 10 Jul 2008 18:50:03 +0200	[thread overview]
Message-ID: <48763DBB.3040708@op5.se> (raw)
In-Reply-To: <4875C1CF.1010604@viscovery.net>

Johannes Sixt wrote:
> Pierre Habouzit schrieb:
>>   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…
> 
> Don't forget to turn it off in the MINGW section in the Makefile since we
> don't have pthreads on Windows.
> 

I started trying that, but ran into problems almost immediately. Enabling
pthreads by default and disabling it for certain systems means we screw
over those poor sods that have their own config.mak files on systems
where there's no <pthread.h> to include, or where that header file
requires a bunch of other stuff to be in first.

On the one hand, that's not nice.
On the other hand, those who have a config.mak are probably savvy enough
figure out how to amend it disable threads as well.

Opinions? I'm all for enabling THREADED_DELTA_SEARCH by default. I've
been using it ever since v1.5.4.3-193-g833e3df when using the same
.gitconfig on all my systems became a sane thing to do and I haven't
seen any ill effects what so ever from it, but how much can we screw
the build-system in place today, and what other systems would, by
default, require the NO_PTHREADS option in the Makefile?

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

  reply	other threads:[~2008-07-10 16: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   ` Andreas Ericsson [this message]
2008-07-10  8:51 ` THREADED_DELTA_SEARCH Jakub Narebski
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=48763DBB.3040708@op5.se \
    --to=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    --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).