git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] add a script to diff rendered documentation

From
Jeff King <peff@peff.net>
Date
Aug 3, 2018, 21:38 UTC
Message-ID
<20180803213819.GA4650@sigill.intra.peff.net>
In-Reply-To
<CAPig+cSDM4vjuhwfuapuPpjjOmXbrhz-i0eVhtShp+nOYReLnA@mail.gmail.com>
On Fri, Aug 03, 2018 at 05:33:17PM -0400, Eric Sunshine wrote:
Show 6 quoted lines
> > +OPTIONS_SPEC="\
> > +doc-diff <from> <to> [-- diff options]
> 
> Should this be?
> 
>     doc-diff [<options>] <from> <to> [-- <diff-options>]

I suppose so. Frankly I only added that line to appease git-sh-options anyway.

Show 6 quoted lines
> > +--
> > +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?
No, they're input to "rev-parse --parseopt".
Show 14 quoted lines
> > +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).
It's git-sh-setup automagic. Try "./doc-diff --foo"
> > +# 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"?
As in, lets the tool "make" reuse results...
-Peff
Previous: Eric SunshineNext: Eric Sunshine
Message 3 of 17 in “add a script to diff rendered documentation”
  1. add a script to diff rendered documentationJeff King, Aug 3, 2018
  2. Eric SunshineAug 3, 2018
  3. Jeff KingAug 3, 2018
  4. Eric SunshineAug 3, 2018
  5. Junio C HamanoAug 3, 2018
  6. Eric SunshineAug 3, 2018
  7. brian m. carlsonAug 5, 2018
  8. Jeff KingAug 6, 2018
  9. Jeff KingAug 6, 2018
  10. Junio C HamanoAug 6, 2018
  11. Jeff KingAug 6, 2018
  12. Jonathan NiederAug 6, 2018
  13. Jeff KingAug 6, 2018
  14. Jeff KingAug 6, 2018
  15. Junio C HamanoAug 6, 2018
  16. Jeff KingAug 6, 2018
  17. Junio C HamanoAug 6, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.