From: Eric Sunshine <sunshine@sunshineco.com>
To: Jeff King <peff@peff.net>
Cc: Git List <git@vger.kernel.org>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] add a script to diff rendered documentation
Date: Fri, 3 Aug 2018 17:33:17 -0400 [thread overview]
Message-ID: <CAPig+cSDM4vjuhwfuapuPpjjOmXbrhz-i0eVhtShp+nOYReLnA@mail.gmail.com> (raw)
In-Reply-To: <20180803205204.GA3790@sigill.intra.peff.net>
On Fri, Aug 3, 2018 at 4:52 PM Jeff King <peff@peff.net> wrote:
> [...]
> Let's provide a script that builds and installs the manpages
> for two commits, renders the results using "man", and diffs
> the result. Since this is time-consuming, we'll also do our
> best to avoid repeated work, keeping intermediate results
> between runs.
> [...]
> Signed-off-by: Jeff King <peff@peff.net>
> ---
> diff --git a/Documentation/doc-diff b/Documentation/doc-diff
> @@ -0,0 +1,100 @@
> +OPTIONS_SPEC="\
> +doc-diff <from> <to> [-- diff options]
Should this be?
doc-diff [<options>] <from> <to> [-- <diff-options>]
> +--
> +j parallel argument to pass to make
> +f force rebuild; do not rely on cached results
> +"
Should "j" and "f" be "-j" and "-f", respectively?
> +while test $# -gt 0
> +do
> + case "$1" in
> + -j)
> + parallel=${1#-j} ;;
> + -f)
> + force=t ;;
> + --)
> + shift; break ;;
> + *)
> + usage ;;
There doesn't seem to a usage() function defined anywhere (and
OPTIONS_SPEC doesn't seem to be used).
> + esac
> + shift
> +done
> +# We'll do both builds in a single worktree, which lets make reuse
> +# results that don't differ between the two trees.
"which lets make reuse"?
next prev parent reply other threads:[~2018-08-03 21:33 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 [this message]
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
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=CAPig+cSDM4vjuhwfuapuPpjjOmXbrhz-i0eVhtShp+nOYReLnA@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).