Re: [PATCH/RFC] thread-utils: better wrapper to avoid #ifdef NO_PTHREADS
- From
Duy Nguyen <pclouds@gmail.com>
- Date
- Oct 27, 2018, 07:26 UTC
- Message-ID
- <CACsJy8D8a-0R=J6nCPwBAypYF=rejgT-3QFnuK1h3vMcJGG7_A@mail.gmail.com>
- In-Reply-To
- <852ad281-09df-c980-790c-df25e82b3331@gmail.com>
On Fri, Oct 26, 2018 at 4:09 PM Ben Peart <peartben@gmail.com> wrote:
Show 5 quoted lines
> I agree though I'm still curious if there are still no-threaded > platforms taking new versions of git. Perhaps we should do the > depreciation warning you suggested elsewhere and see how much push back > we get. It's unlikely we'd get lucky and be able to stop supporting > them completely but it's worth asking!
NO_PTHREADS can also be used even though the platform supports multithread: to make keep git execution in a single core/thread. It might matter on hosted systems with limited cpu power and you don't want git to hog it all. Yes it can also be achieved by setting a zillion config keys to "1", this way is just simpler.
-- Duy