From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH/RFC] thread-utils: better wrapper to avoid #ifdef NO_PTHREADS
Date: Wed, 24 Oct 2018 11:58:43 +0900 [thread overview]
Message-ID: <xmqq1s8gqcd8.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20181023202842.GA17371@sigill.intra.peff.net> (Jeff King's message of "Tue, 23 Oct 2018 16:28:43 -0400")
Jeff King <peff@peff.net> writes:
> I also think we may want to make a fundamental shift in our view of
> thread support. In the early days, it was "well, this is a thing that
> modern systems can take advantage of for certain commands". But these
> days I suspect it is more like "there are a handful of legacy systems
> that do not even support threads".
>
> I don't think we should break the build on those legacy systems, but
> it's probably OK to stop thinking of it as "non-threaded platforms are
> the default and must pay zero cost" and more as "threaded platforms are
> the default, and non-threaded ones are OK to pay a small cost as long as
> they still work".
Good suggestion.
next prev parent reply other threads:[~2018-10-24 2:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 7:05 [PATCH] config.mak.dev: enable -Wunused-function Jeff King
2018-10-18 7:08 ` Jeff King
2018-10-18 15:48 ` Duy Nguyen
2018-10-18 17:09 ` Jeff King
2018-10-18 18:05 ` [PATCH/RFC] thread-utils: better wrapper to avoid #ifdef NO_PTHREADS Nguyễn Thái Ngọc Duy
2018-10-23 20:28 ` Jeff King
2018-10-24 2:58 ` Junio C Hamano [this message]
2018-10-26 14:09 ` Ben Peart
2018-10-27 7:12 ` can we deprecate NO_PTHREADS?, was: " Jeff King
2018-10-27 7:26 ` [PATCH/RFC] thread-utils: " Duy Nguyen
2018-10-27 8:17 ` Jeff King
2018-10-18 17:01 ` [PATCH] config.mak.dev: enable -Wunused-function Ramsay Jones
2018-10-19 1:23 ` Junio C Hamano
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=xmqq1s8gqcd8.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
/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).