From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>, git@vger.kernel.org
Subject: Re: [PATCH] add a script to diff rendered documentation
Date: Mon, 06 Aug 2018 08:16:47 -0700 [thread overview]
Message-ID: <xmqqd0uvr0dc.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20180806134237.GB31282@sigill.intra.peff.net> (Jeff King's message of "Mon, 6 Aug 2018 09:42:38 -0400")
Jeff King <peff@peff.net> writes:
> On Mon, Aug 06, 2018 at 09:39:55AM -0400, Jeff King wrote:
>
>> 3. Default to number of CPUs, which is what a lot of other threading
>> in Git does. Unfortunately getting that from the shell is
>> non-trivial. I'm OK with $(grep -c ^processor /proc/cpuinfo), but
>> people on non-Linux platforms would have to fill in their own
>> implementation.
>
> Is this too horrible to contemplate?
Chickens, eggs and a kitchen sink. Sounds like a title of a movie.
It's a bit dissapointing that we cannot express personal preference
in config.mak ;-)
> diff --git a/builtin/rev-parse.c b/builtin/rev-parse.c
> index 0f09bbbf65..fa8caeec0c 100644
> --- a/builtin/rev-parse.c
> +++ b/builtin/rev-parse.c
> @@ -635,6 +635,11 @@ int cmd_rev_parse(int argc, const char **argv, const char *prefix)
> continue;
> }
>
> + if (!strcmp(arg, "--online-cpus")) {
> + printf("%d", online_cpus());
> + continue;
> + }
> +
> /* The rest of the options require a git repository. */
> if (!did_repo_setup) {
> prefix = setup_git_directory();
>
> -Peff
next prev parent reply other threads:[~2018-08-06 15:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 20:52 [PATCH] add a script to diff rendered documentation Jeff King
2018-08-03 21:33 ` Eric Sunshine
2018-08-03 21:38 ` Jeff King
2018-08-03 21:44 ` Eric Sunshine
2018-08-03 21:47 ` Junio C Hamano
2018-08-03 22:41 ` Eric Sunshine
2018-08-05 20:49 ` brian m. carlson
2018-08-06 13:39 ` Jeff King
2018-08-06 13:42 ` Jeff King
2018-08-06 15:16 ` Junio C Hamano [this message]
2018-08-06 16:57 ` Jeff King
2018-08-06 15:01 ` Jonathan Nieder
2018-08-06 16:42 ` Jeff King
2018-08-06 17:37 ` Jeff King
2018-08-06 18:25 ` Junio C Hamano
2018-08-06 18:58 ` Jeff King
2018-08-06 19:29 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqd0uvr0dc.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).