From: Christian Couder <chriscool@tuxfamily.org>
To: Junio Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/3] Uncomment test case: git branch c/d should barf if branch c exists.
Date: Sat, 24 Mar 2007 06:34:52 +0100 [thread overview]
Message-ID: <200703240634.52771.chriscool@tuxfamily.org> (raw)
In-Reply-To: <20070324063021.2520da21.chriscool@tuxfamily.org>
Oops, sorry this one is also an old mail that was in my Draft folder and
should not have been sent...
Christian.
Le samedi 24 mars 2007 06:30, Christian Couder a écrit :
> Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
> ---
> t/t3210-pack-refs.sh | 12 ++++++------
> 1 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/t/t3210-pack-refs.sh b/t/t3210-pack-refs.sh
> index 2cc03e6..193fe1f 100755
> --- a/t/t3210-pack-refs.sh
> +++ b/t/t3210-pack-refs.sh
> @@ -37,12 +37,12 @@ test_expect_success \
> git-show-ref b >result &&
> diff expect result'
>
> -# test_expect_failure \
> -# 'git branch c/d should barf if branch c exists' \
> -# 'git-branch c &&
> -# git-pack-refs &&
> -# rm .git/refs/heads/c &&
> -# git-branch c/d'
> +test_expect_failure \
> + 'git branch c/d should barf if branch c exists' \
> + 'git-branch c &&
> + git-pack-refs &&
> + rm .git/refs/heads/c &&
> + git-branch c/d'
>
> test_expect_success \
> 'see if a branch still exists after git pack-refs --prune' \
next prev parent reply other threads:[~2007-03-24 5:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060928065845.38de4f94.chriscool@tuxfamily.org>
2007-03-24 5:30 ` [PATCH 3/3] Uncomment test case: git branch c/d should barf if branch c exists Christian Couder
2007-03-24 5:34 ` Christian Couder [this message]
2006-09-28 5:02 Christian Couder
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=200703240634.52771.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).