All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: larsxschneider@gmail.com
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH v1] travis-ci: build documentation
Date: Fri, 22 Apr 2016 11:07:31 +0200	[thread overview]
Message-ID: <vpq37qeovu4.fsf@anie.imag.fr> (raw)
In-Reply-To: <1461314042-3132-1-git-send-email-larsxschneider@gmail.com> (larsxschneider@gmail.com's message of "Fri, 22 Apr 2016 10:34:02 +0200")

larsxschneider@gmail.com writes:

> +      if [[ "$TRAVIS_OS_NAME" = linux ]] && [[ "$CC" = gcc ]];

[[ is a bashism, and doesn't bring anything here compared to the POSIX
[ ... ], or "test" which is prefered in Git's source code.

The ; or the newline is not needed either.

I'd write

if test "$TRAVIS_OS_NAME" = linux && test "$CC" = gcc; then

> +          then
> +          echo ""
> +          echo "------------------------------------------------------------------------" &&

I usualy avoid "echo <something-starting-with-dash>" as I'm not sure how
portable it is across variants of "echo". Maybe this one is portable
enough, I don't know. Perhaps printf, or cat << EOF ...?

> +          echo "$(tput setaf 2)Building documentation...$(tput sgr0)" &&
> +          make --quiet doc
> +      fi;

Nit: useless ;

I think it makes sense to do some lightweight checks after "make doc",
rather than just check the return code. For example, check that a few
generated files exist and are non-empty, like

test -s Documentation/git.html &&
test -s Documentation/git.1

Thanks,

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

  reply	other threads:[~2016-04-22  9:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22  8:34 [PATCH v1] travis-ci: build documentation larsxschneider
2016-04-22  9:07 ` Matthieu Moy [this message]
2016-04-22 18:14   ` Junio C Hamano
2016-04-25  8:33     ` Lars Schneider
2016-04-25 16:56       ` Junio C Hamano
2016-04-25 19:03         ` Junio C Hamano
2016-04-25 19:32           ` Matthieu Moy
2016-04-25 19:46             ` Junio C Hamano
2016-04-25  9:26     ` Matthieu Moy
2016-04-25  8:17   ` Lars Schneider
2016-04-25  9:37     ` Matthieu Moy
2016-04-22 10:45 ` stefan.naewe
2016-04-25  8:20   ` Lars Schneider
2016-04-23  3:39 ` Jeff King
2016-04-25  8:35   ` Lars Schneider
2016-04-25 17:07     ` Jeff King

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vpq37qeovu4.fsf@anie.imag.fr \
    --to=matthieu.moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=larsxschneider@gmail.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.