From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>
Subject: [PATCH 2/4] t6018: add tests for rev-list's --branches and --tags
Date: Thu, 13 May 2010 16:24:36 +0200 [thread overview]
Message-ID: <ee2e0da5718c16fbfe65c61de85da8955bb52c63.1273760226.git.git@drmicha.warpmail.net> (raw)
In-Reply-To: <20100505033536.GB8779@coredump.intra.peff.net>
In-Reply-To: <cover.1273760226.git.git@drmicha.warpmail.net>
so that we know when they break.
Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
---
t/t6018-rev-list-glob.sh | 13 +++++++++++++
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/t/t6018-rev-list-glob.sh b/t/t6018-rev-list-glob.sh
index 8d3fa7d..dbedc4d 100755
--- a/t/t6018-rev-list-glob.sh
+++ b/t/t6018-rev-list-glob.sh
@@ -162,6 +162,13 @@ test_expect_success 'rev-list --branches=subspace' '
compare rev-list "subspace/one subspace/two" "--branches=subspace"
'
+
+test_expect_success 'rev-list --branches' '
+
+ compare rev-list "master subspace-x someref other/three subspace/one subspace/two" "--branches"
+
+'
+
test_expect_success 'rev-list --glob=heads/someref/* master' '
compare rev-list "master" "--glob=heads/someref/* master"
@@ -186,6 +193,12 @@ test_expect_success 'rev-list --tags=foo' '
'
+test_expect_success 'rev-list --tags' '
+
+ compare rev-list "foo/bar" "--tags"
+
+'
+
test_expect_success 'rev-list --remotes=foo' '
compare rev-list "foo/baz" "--remotes=foo"
--
1.7.1.240.geeaa4d
next prev parent reply other threads:[~2010-05-13 14:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-01 18:36 [RFD PATCH] revlist/rev-parse: Introduce --heads and --locals revision specifiers Michael J Gruber
2010-05-01 19:42 ` Jakub Narebski
2010-05-01 19:47 ` Michael J Gruber
2010-05-01 19:51 ` Jakub Narebski
2010-05-02 5:00 ` Jeff King
2010-05-02 13:43 ` Michael J Gruber
2010-05-05 3:35 ` Jeff King
2010-05-13 14:24 ` [PATCH 0/4] All is too much Michael J Gruber
2010-05-13 14:24 ` [PATCH 1/4] rev-parse: deprecate use as an option sifter Michael J Gruber
2010-05-14 15:41 ` Jakub Narebski
2010-05-14 18:52 ` Michael J Gruber
2010-05-14 19:01 ` Jakub Narebski
2010-05-14 19:22 ` Michael J Gruber
2010-05-17 14:26 ` Thomas Rast
2010-05-13 14:24 ` Michael J Gruber [this message]
2010-05-13 14:24 ` [PATCH 3/4] t6018: make sure all tested symbolic names are different revs Michael J Gruber
2010-05-13 14:24 ` [PATCH 4/4] revlist: Introduce --lrbranches and --locals revision specifiers Michael J Gruber
2010-05-14 6:06 ` [PATCH 0/4] All is too much Jeff King
2010-05-14 16:08 ` Michael J Gruber
2010-05-14 16:14 ` Git methodology question Akhbari, Farshad
2010-05-14 21:44 ` Chris Packham
2010-05-14 21:54 ` Avery Pennarun
2010-05-14 18:26 ` [PATCH v2 0/4] All is too much Michael J Gruber
2010-05-14 18:26 ` [PATCH v2 1/4] rev-parse: deprecate use as an option sifter Michael J Gruber
2010-05-14 18:26 ` [PATCH v2 2/4] t6018: add tests for rev-list's --branches and --tags Michael J Gruber
2010-05-14 18:26 ` [PATCH v2 3/4] t6018: make sure all tested symbolic names are different revs Michael J Gruber
2010-05-14 18:26 ` [PATCH v2 4/4] revlist: Introduce --lrbranches and --locals revision specifiers Michael J Gruber
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=ee2e0da5718c16fbfe65c61de85da8955bb52c63.1273760226.git.git@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).