From: Frederic Heitzmann <frederic.heitzmann@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, bjacobs@woti.com, rchen@cs.umd.edu
Subject: Re: [PATCH] Disambiguate duplicate t9160* tests
Date: Fri, 16 Sep 2011 23:16:54 +0200 [thread overview]
Message-ID: <4E73BCC6.2030303@gmail.com> (raw)
In-Reply-To: <7viposdwos.fsf@alter.siamese.dyndns.org>
Le 16/09/2011 23:06, Junio C Hamano a écrit :
> Junio C Hamano<gitster@pobox.com> writes:
>
>> Thanks.
>
> Heh, I spoke too early. It still refers to contents of t/t9160/ directory.
> We would need this squashed into your patch (no need to resend).
>
> t/t9161-git-svn-mergeinfo-push.sh | 2 +-
> t/{t9160 => t9161}/branches.dump | 0
> 2 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/t/t9161-git-svn-mergeinfo-push.sh b/t/t9161-git-svn-mergeinfo-push.sh
> index 216f3d7..6ef0c0b 100755
> --- a/t/t9161-git-svn-mergeinfo-push.sh
> +++ b/t/t9161-git-svn-mergeinfo-push.sh
> @@ -10,7 +10,7 @@ test_description='git-svn svn mergeinfo propagation'
>
> test_expect_success 'load svn dump' "
> svnadmin load -q '$rawsvnrepo' \
> - < '$TEST_DIRECTORY/t9160/branches.dump'&&
> + < '$TEST_DIRECTORY/t9161/branches.dump'&&
> git svn init --minimize-url -R svnmerge \
> -T trunk -b branches '$svnrepo'&&
> git svn fetch --all
> diff --git a/t/t9160/branches.dump b/t/t9161/branches.dump
> similarity index 100%
> rename from t/t9160/branches.dump
> rename to t/t9161/branches.dump
Ooops ! I checked 'make test', but missed the most obvious change.
Sorry for this.
--
Fred
prev parent reply other threads:[~2011-09-16 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 19:55 [PATCH] Disambiguate duplicate t9160* tests Frédéric Heitzmann
2011-09-16 20:41 ` Junio C Hamano
2011-09-16 21:06 ` Junio C Hamano
2011-09-16 21:16 ` Frederic Heitzmann [this message]
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=4E73BCC6.2030303@gmail.com \
--to=frederic.heitzmann@gmail.com \
--cc=bjacobs@woti.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rchen@cs.umd.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 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).