From: Phil Hord <hordp@cisco.com>
To: Greg Price <price@MIT.EDU>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 6/6] rebase --rewrite-refs: tests
Date: Mon, 27 Jun 2011 12:07:10 -0400 [thread overview]
Message-ID: <4E08AAAE.5020604@cisco.com> (raw)
In-Reply-To: <ab6d17ba0ea919e0f873597b60d6c7e9a43460c8.1309133817.git.greg@quora.com>
On 01/24/2010 09:28 PM, Greg Price wrote:
> Signed-off-by: Greg Price <price@mit.edu>
> ---
> t/t3420-rebase-ref.sh | 75 +++++++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 75 insertions(+), 0 deletions(-)
> create mode 100644 t/t3420-rebase-ref.sh
>
> diff --git a/t/t3420-rebase-ref.sh b/t/t3420-rebase-ref.sh
> new file mode 100644
> index 0000000..601a434
> --- /dev/null
> +++ b/t/t3420-rebase-ref.sh
> @@ -0,0 +1,75 @@
> +#!/bin/sh
> +
> +test_description='git rebase --rewrite-refs'
> +
> +. ./test-lib.sh
> +. "$TEST_DIRECTORY/lib-rebase.sh"
> +set_fake_editor
> +
> +# part1 part2 topic
> +# | | |
> +# v v v
> +# A-----C------D-----E
> +# \
> +# B <--master
> +
> +test_expect_success setup '
> + test_commit A &&
> + git branch topic &&
> + test_commit B &&
> + git checkout topic &&
> + test_commit C &&
> + git branch part1 &&
> + test_commit D
> + git branch part2 &&
> + test_commit E
> +'
I think there is a missing "&&" at the end of "test_commit D". But it's
possible I just don't understand the test machinery enough to know this
is normal. Can you explain to me the difference in that case?
Phil
next prev parent reply other threads:[~2011-06-27 16:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 0:16 [PATCH 0/6] rebase: command "ref" and options --rewrite-{refs,heads,tags} Greg Price
2009-10-10 2:52 ` [PATCH 1/6] rebase -i: Add the "ref" command Greg Price
2011-06-27 18:46 ` Junio C Hamano
2011-06-28 11:15 ` Greg Price
2009-11-18 23:22 ` [PATCH 2/6] pretty: Add %D for script-friendly decoration Greg Price
2011-06-27 19:07 ` Junio C Hamano
2009-11-18 23:51 ` [PATCH 4/6] rebase: --rewrite-{refs,heads,tags} to pull refs along with branch Greg Price
2011-06-27 16:11 ` Phil Hord
2011-06-28 11:19 ` Greg Price
2010-01-07 23:08 ` [PATCH 3/6] for-each-ref: --stdin to match specified refs against pattern Greg Price
2010-01-25 2:26 ` [PATCH 5/6] t/lib-rebase.sh: pass through ref commands Greg Price
2010-01-25 2:28 ` [PATCH 6/6] rebase --rewrite-refs: tests Greg Price
2011-06-27 16:07 ` Phil Hord [this message]
2011-06-28 11:22 ` Greg Price
2011-06-27 21:02 ` Junio C Hamano
2011-06-28 11:20 ` Greg Price
2011-06-27 18:36 ` [PATCH 0/6] rebase: command "ref" and options --rewrite-{refs,heads,tags} Junio C Hamano
2011-06-28 10:47 ` Fwd: " Greg Price
2011-06-28 13:17 ` Greg Price
2011-06-30 4:25 ` Ramkumar Ramachandra
2011-08-03 13:32 ` Fwd: " Sverre Rabbelier
2011-08-03 22:31 ` Greg Price
2011-06-27 21:23 ` Junio C Hamano
2011-06-28 10:56 ` Fwd: " Greg Price
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=4E08AAAE.5020604@cisco.com \
--to=hordp@cisco.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=price@MIT.EDU \
/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.