From: Bert Wesarg <bert.wesarg@googlemail.com>
To: Jeff King <peff@peff.net>
Cc: Johan Herland <johan@herland.net>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [PATCH] Add known breakage for 'git notes copy'
Date: Mon, 28 Jun 2010 11:12:01 +0200 [thread overview]
Message-ID: <AANLkTimap7ziJ-NuAV6h7bGP3cX2cDY7rqEbgJ2unQSP@mail.gmail.com> (raw)
In-Reply-To: <20100628085907.GA14014@coredump.intra.peff.net>
On Mon, Jun 28, 2010 at 10:59, Jeff King <peff@peff.net> wrote:
> On Mon, Jun 28, 2010 at 09:01:57AM +0200, Bert Wesarg wrote:
>
>> 'git notes copy' dumps core when no arguments are given.
>
> How about:
Thanks.
Tested-by: Bert Wesarg <Bert.Wesarg@googlemail.com>
FWIW, here is the correct and updated test for this:
-- >8 --
Subject: [PATCH] notes: add test for git-notes copy with too few arguments
Signed-off-by: Bert Wesarg <bert.wesarg@googlemail.com>
---
t/t3301-notes.sh | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/t/t3301-notes.sh b/t/t3301-notes.sh
index 64f32ad..dcd962a 100755 t/t3301-notes.sh
--- a/t/t3301-notes.sh
+++ b/t/t3301-notes.sh
@@ -1044,4 +1044,9 @@ test_expect_success 'GIT_NOTES_REWRITE_REF
overrides config' '
git log -1 > output &&
test_cmp expect output
'
+
+test_expect_success 'git notes copy does not segfaults with too few
arguments' '
+ test_must_fail git notes copy
+'
+
test_done
next prev parent reply other threads:[~2010-06-28 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 7:01 [PATCH] Add known breakage for 'git notes copy' Bert Wesarg
2010-06-28 8:59 ` Jeff King
2010-06-28 9:12 ` Bert Wesarg [this message]
2010-06-28 15:44 ` Jacob Helwig
2010-06-28 22:48 ` Johan Herland
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=AANLkTimap7ziJ-NuAV6h7bGP3cX2cDY7rqEbgJ2unQSP@mail.gmail.com \
--to=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johan@herland.net \
--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).