git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <bebarino@gmail.com>
To: git@vger.kernel.org
Cc: Thomas Adam <thomas.adam22@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	Johannes Sixt <j.sixt@viscovery.net>
Subject: [PATCHv4 0/5] Teach shell scripts to be quiet
Date: Tue, 16 Jun 2009 15:32:56 -0700	[thread overview]
Message-ID: <1245191581-11127-1-git-send-email-bebarino@gmail.com> (raw)
In-Reply-To: <1245117905-19351-1-git-send-email-bebarino@gmail.com>

The main goal of this series is to teach git-am and git-rebase to be
quiet.

This series feels very improved. I'm pretty confident in the first
three patches. I've split off the suppressing errors from git-apply
in git-am into its own patch this time around. It felt more like
an independent change.

I've tried to make sure I maintained GIT_QUIET after failing to apply,
but I'd appreciate if others could look over that to make sure.

Changes since v3:
    - simplify say()
    - say "applying to an empty history" in am.sh
    - quiet merge in rebase.sh::call_merge()
    - drop >&2 in a couple places in rebase.sh
    - maintain GIT_QUIET when git-am or git-rebase fails
    - fixup style issues with repack.sh
    - add to git_am_opt instead of hijacking GIT_QUIET in rebase.sh

Changes since v2:
    - say uses printf instead of echo
    - suppressing errors from git-apply under am -3 -q
    - added a test for am -3 -q
    - added a test for am where subjects have a literal newline
    - am,rebase tests check both stdout and stderr
    - rebase.sh::continue_merge() suppress the output of git rev-list

Changes since v1:
    - introduction of say()
    - migration of submodule and repack

Stephen Boyd (5):
  t4150: test applying with a newline in subject
  am: suppress apply errors when using 3-way
  git-sh-setup: introduce say() for quiet options
  submodule, repack: migrate to git-sh-setup's say()
  am, rebase: teach quiet option

 Documentation/git-am.txt     |    6 ++++-
 Documentation/git-rebase.txt |    4 +++
 git-am.sh                    |   35 +++++++++++++++++++++++-------
 git-rebase.sh                |   48 +++++++++++++++++++++++++++++++++--------
 git-repack.sh                |   12 ++++------
 git-sh-setup.sh              |    9 +++++++
 git-submodule.sh             |   24 +++++---------------
 t/t3400-rebase.sh            |   19 +++++++++++-----
 t/t4150-am.sh                |   26 ++++++++++++++++++++++
 9 files changed, 133 insertions(+), 50 deletions(-)

  parent reply	other threads:[~2009-06-16 22:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16  2:05 [PATCHv3 0/4] Teach shell scripts to be quiet Stephen Boyd
2009-06-16  2:05 ` [PATCHv3 1/4] t4150: test applying with a newline in subject Stephen Boyd
2009-06-16  2:05   ` [PATCHv3 2/4] git-sh-setup: introduce say() for quiet options Stephen Boyd
2009-06-16  2:05     ` [PATCHv3 3/4] submodule, repack: migrate to git-sh-setup's say() Stephen Boyd
2009-06-16  2:05       ` [PATCHv3 4/4] am, rebase: teach quiet option Stephen Boyd
2009-06-16  5:57         ` Junio C Hamano
2009-06-16  7:50           ` Stephen Boyd
2009-06-16  5:56       ` [PATCHv3 3/4] submodule, repack: migrate to git-sh-setup's say() Junio C Hamano
2009-06-16  6:18         ` Junio C Hamano
2009-06-16  7:38         ` Stephen Boyd
2009-06-16  8:13     ` [PATCHv3 2/4] git-sh-setup: introduce say() for quiet options Johannes Sixt
2009-06-16 22:32 ` Stephen Boyd [this message]
2009-06-16 22:32   ` [PATCHv4 1/5] t4150: test applying with a newline in subject Stephen Boyd
2009-06-16 22:32     ` [PATCHv4 2/5] am: suppress apply errors when using 3-way Stephen Boyd
2009-06-16 22:32       ` [PATCHv4 3/5] git-sh-setup: introduce say() for quiet options Stephen Boyd
2009-06-16 22:33         ` [PATCHv4 4/5] submodule, repack: migrate to git-sh-setup's say() Stephen Boyd
2009-06-16 22:33           ` [PATCHv4 5/5] am, rebase: teach quiet option Stephen Boyd
2009-06-18  1:07             ` [PATCHv4 6/5] stash: " Stephen Boyd

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=1245191581-11127-1-git-send-email-bebarino@gmail.com \
    --to=bebarino@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j.sixt@viscovery.net \
    --cc=thomas.adam22@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 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 NNTP newsgroup(s).