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

Re: [PATCHv2 1/3] git-sh-setup: introduce say() for quiet options

From
Thomas Adam <thomas.adam22@gmail.com>
Date
Jun 14, 2009, 23:21 UTC
Message-ID
<18071eea0906141621t676a965aqc3056b481b8e8796@mail.gmail.com>
In-Reply-To
<1245021374-8430-2-git-send-email-bebarino@gmail.com>
2009/6/15 Stephen Boyd <bebarino@gmail.com>:
Show 21 quoted lines
> Scripts should use say() when they want to echo to stdout. Setting
> GIT_QUIET will mute say(), allowing scripts to easily implement a quiet
> option.
>
> Signed-off-by: Stephen Boyd <bebarino@gmail.com>
> ---
>  git-sh-setup.sh |    7 +++++++
>  1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/git-sh-setup.sh b/git-sh-setup.sh
> index 80acb7d..f88184e 100755
> --- a/git-sh-setup.sh
> +++ b/git-sh-setup.sh
> @@ -44,6 +44,13 @@ die() {
>        exit 1
>  }
>
> +say () {
> +       if test -z "$GIT_QUIET"
> +       then
> +               echo "$@"

Except that where you've then replaced various calls with say() they were originally using printf. Please use printf here also, and not echo.

-- Thomas Adam
Previous: Stephen BoydNext: Junio C Hamano
Message 14 of 18 in “teach am and rebase -q/--quiet”
  1. 0/2 teach am and rebase -q/--quietStephen Boyd, Jun 13, 2009
  2. 1/2 am: teach quiet optionStephen Boyd, Jun 13, 2009
  3. 2/2 rebase: teach quiet optionStephen Boyd, Jun 13, 2009
  4. Junio C HamanoJun 13, 2009
  5. Stephen BoydJun 14, 2009
  6. Sverre RabbelierJun 14, 2009
  7. Junio C HamanoJun 13, 2009
  8. Stephen BoydJun 14, 2009
  9. Junio C HamanoJun 14, 2009
  10. 0/3 Teach shell scripts to be quietStephen Boyd, Jun 14, 2009
  11. 1/3 git-sh-setup: introduce say() for quiet optionsStephen Boyd, Jun 14, 2009
  12. 2/3 submodule, repack: migrate to git-sh-setup's say()Stephen Boyd, Jun 14, 2009
  13. 3/3 am, rebase: teach quiet optionStephen Boyd, Jun 14, 2009
  14. Thomas AdamJun 14, 2009
  15. Junio C HamanoJun 15, 2009
  16. Stephen BoydJun 15, 2009
  17. Johannes SixtJun 15, 2009
  18. Stephen BoydJun 15, 2009

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.