From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: Eric Sunshine <sunshine@sunshineco.com>,
Junio C Hamano <gitster@pobox.com>,
Michael J Gruber <git@drmicha.warpmail.net>
Subject: [PATCH 0/5] --format=%G tests and fixes
Date: Mon, 16 Jun 2014 19:59:17 -0400 [thread overview]
Message-ID: <20140616235917.GA19499@sigill.intra.peff.net> (raw)
In-Reply-To: <20140616233649.GA12350@sigill.intra.peff.net>
On Mon, Jun 16, 2014 at 07:36:49PM -0400, Jeff King wrote:
> On Mon, Jun 16, 2014 at 05:50:14PM -0400, Eric Sunshine wrote:
>
> > > +test_expect_success GPG 'show good signature with custom format' '
> > > + cat >expect <<-\EOF
> >
> > Broken &&-chain (and in tests below).
>
> Whoops, thanks. Re-roll coming in a minute. I'm also reorganizing the
> two patches a bit and adding a test for an unvalidated key.
OK, here they are. Somehow it multiplied into 5 patches. I must have
gotten them wet.
[1/5]: t7510: stop referring to master in later tests
[2/5]: t7510: use consistent &&-chains in loop
[3/5]: t7510: test a commit signed by an unknown key
[4/5]: t7510: check %G* pretty-format output
[5/5]: pretty: avoid reading past end-of-string with "%G"
-Peff
next prev parent reply other threads:[~2014-06-16 23:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 20:13 [PATCH] pretty: avoid reading past end-of-string with "%G" Jeff King
2014-06-16 20:26 ` [PATCH] t7510: check %G* pretty-format output Jeff King
2014-06-16 21:50 ` Eric Sunshine
2014-06-16 23:36 ` Jeff King
2014-06-16 23:59 ` Jeff King [this message]
2014-06-16 23:59 ` [PATCH 1/5] t7510: stop referring to master in later tests Jeff King
2014-06-17 0:03 ` [PATCH 2/5] t7510: use consistent &&-chains in loop Jeff King
2014-06-17 0:05 ` [PATCH 3/5] t7510: test a commit signed by an unknown key Jeff King
2014-06-17 0:06 ` [PATCH 4/5] t7510: check %G* pretty-format output Jeff King
2014-06-17 0:07 ` [PATCH 5/5] pretty: avoid reading past end-of-string with "%G" Jeff King
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=20140616235917.GA19499@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sunshine@sunshineco.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).