From: Michael Haggerty <mhagger@alum.mit.edu>
To: Stefan Beller <sbeller@google.com>,
jrnieder@gmail.com, gitster@pobox.com, ronniesahlberg@gmail.com,
git@vger.kernel.org
Cc: Ronnie Sahlberg <sahlberg@google.com>
Subject: Re: [PATCHv2] branch -d: test if we can delete broken refs
Date: Wed, 26 Nov 2014 09:49:03 +0100 [thread overview]
Message-ID: <547593FF.6040507@alum.mit.edu> (raw)
In-Reply-To: <1416963565-32318-1-git-send-email-sbeller@google.com>
Aside from one tiny formatting nit (see below), the test looks good to
me. On the other hand, this is kind of an "aspirational test"; I don't
know that the tested functionality has ever worked or that anybody has
ever claimed that it works. So my feeling is that the addition of the
test would feel more natural in the patch series that implements the new
feature. But I don't feel strongly about it.
Michael
On 11/26/2014 01:59 AM, Stefan Beller wrote:
> From: Ronnie Sahlberg <sahlberg@google.com>
>
> Signed-off-by: Ronnie Sahlberg <sahlberg@google.com>
> Signed-off-by: Stefan Beller <sbeller@google.com>
> ---
> Changes v1->v2
> * relocated the test from t1402 to t3200
> * reword the commit message title to fit in with similar commits touching
> t/t3200-branch.sh
>
> t/t3200-branch.sh | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/t/t3200-branch.sh b/t/t3200-branch.sh
> index 432921b..fa7d7bd 100755
> --- a/t/t3200-branch.sh
> +++ b/t/t3200-branch.sh
> @@ -163,6 +163,14 @@ test_expect_success 'git branch --list -d t should fail' '
> test_path_is_missing .git/refs/heads/t
> '
>
> +test_expect_failure 'git branch -d can delete ref with broken sha1' '
> + echo "pointing nowhere" > .git/refs/heads/brokensha1 &&
Please no space between the ">" and the filename.
> + test_when_finished "rm -f .git/refs/heads/brokensha1" &&
> + git branch -d brokensha1 &&
> + git branch >output &&
> + ! grep -e "brokensha1" output
> +'
> +
> test_expect_success 'git branch --column' '
> COLUMNS=81 git branch --column=column >actual &&
> cat >expected <<\EOF &&
>
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2014-11-26 8:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 22:56 [PATCH] t1402: check to delete broken refs Stefan Beller
2014-11-26 0:35 ` Jonathan Nieder
2014-11-26 0:42 ` Stefan Beller
2014-11-26 0:59 ` [PATCHv2] branch -d: test if we can " Stefan Beller
2014-11-26 8:49 ` Michael Haggerty [this message]
2014-11-26 18:43 ` Junio C Hamano
2014-11-26 5:05 ` [PATCH] t1402: check to " Torsten Bögershausen
2014-11-26 18:37 ` [PATCHv3] branch -d: test if we can " Stefan Beller
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=547593FF.6040507@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=ronniesahlberg@gmail.com \
--cc=sahlberg@google.com \
--cc=sbeller@google.com \
/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).