All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Karl Hasselström" <kha@treskal.com>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: [StGit PATCH 0/5] test suite update
Date: Thu, 17 Apr 2008 23:12:40 +0200	[thread overview]
Message-ID: <20080417210137.12809.88457.stgit@yoghurt> (raw)

This patch series pulls in updates to test-lib.sh from git (we now get
colored output!), and does some other assorted test suite updates.

---

Karl Hasselström (5):
      Use test_cmp instead of diff -u in the test suite
      Get rid of backticks in test-lib.sh
      Steal more test-lib.sh updates from git
      Use hardcoded author and committer names in tests
      If a patch is not changed when pushing, reuse the same commit object


 stgit/lib/transaction.py |   11 ++-
 t/t0002-status.sh        |   32 ++++----
 t/t1201-pull-trailing.sh |    2 
 t/t2700-refresh.sh       |   12 +--
 t/t2800-goto-subdir.sh   |    8 +-
 t/test-lib.sh            |  189 +++++++++++++++++++++++++++++++++++-----------
 6 files changed, 179 insertions(+), 75 deletions(-)

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle

             reply	other threads:[~2008-04-17 21:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-17 21:12 Karl Hasselström [this message]
2008-04-17 21:12 ` [StGit PATCH 1/5] If a patch is not changed when pushing, reuse the same commit object Karl Hasselström
2008-04-17 21:12 ` [StGit PATCH 2/5] Use hardcoded author and committer names in tests Karl Hasselström
2008-04-17 21:12 ` [StGit PATCH 3/5] Steal more test-lib.sh updates from git Karl Hasselström
2008-04-17 21:13 ` [StGit PATCH 4/5] Get rid of backticks in test-lib.sh Karl Hasselström
2008-04-17 21:13 ` [StGit PATCH 5/5] Use test_cmp instead of diff -u in the test suite Karl Hasselström
2008-04-17 21:14 ` [StGit PATCH 0/5] test suite update Karl Hasselström

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=20080417210137.12809.88457.stgit@yoghurt \
    --to=kha@treskal.com \
    --cc=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    /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.