From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Eric Sunshine <sunshine@sunshineco.com>,
Jonathan Nieder <jrnieder@gmail.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: [PATCH] add a script to diff rendered documentation
Date: Mon, 06 Aug 2018 11:25:07 -0700 [thread overview]
Message-ID: <xmqqy3djnyik.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20180806173720.GA5508@sigill.intra.peff.net> (Jeff King's message of "Mon, 6 Aug 2018 13:37:20 -0400")
Jeff King <peff@peff.net> writes:
> +while test $# -gt 0
> +do
> + case "$1" in
> + -j)
> + parallel=${1#-j} ;;
This is curious. Did you mean "-j*)" on the line above this one?
> + -f)
> + force=t ;;
> + --)
> + shift; break ;;
> + *)
> + usage ;;
> + esac
> + shift
> +done
> +
> +if test -z "$parallel"
> +then
Then "script -j" (no explicit number) would get here and autodetect.
Running the script without any "-j" would also get an empty parallel
and come here.
So "script -j1" would be how a user would say "I want to use exactly
one process, not any parallelism", which makes sense.
> + parallel=$(getconf _NPROCESSORS_ONLN 2>/dev/null)
> + if test $? != 0 || test -z "$parallel"
> + then
> + parallel=1
> + fi
> +fi
next prev parent reply other threads:[~2018-08-06 18:25 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
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 [this message]
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=xmqqy3djnyik.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=sunshine@sunshineco.com \
/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).