All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, santiago@nyu.edu, gitster@pobox.com,
	peff@peff.net, sunshine@sunshineco.com, walters@verbum.org
Subject: Re: What's cooking in git.git (Oct 2016, #09; Mon, 31)
Date: Sat, 5 Nov 2016 07:42:31 +0000	[thread overview]
Message-ID: <20161105074231.GA15803@tb-raspi> (raw)
In-Reply-To: <xmqqwpgoqjct.fsf@gitster.mtv.corp.google.com>

> * st/verify-tag (2016-10-10) 7 commits
>  - t/t7004-tag: Add --format specifier tests
>  - t/t7030-verify-tag: Add --format specifier tests
>  - builtin/tag: add --format argument for tag -v
>  - builtin/verify-tag: add --format to verify-tag
>  - tag: add format specifier to gpg_verify_tag
>  - ref-filter: add function to print single ref_array_item
>  - gpg-interface, tag: add GPG_VERIFY_QUIET flag
> 
>  "git tag" and "git verify-tag" learned to put GPG verification
>  status in their "--format=<placeholders>" output format.
> 
>  Waiting for a reroll.
>  cf. <20161007210721.20437-1-santiago@nyu.edu>

I don't know if this has been reported before:
Some tests needs to be protected by GPG:
+test_expect_success GPG 'verifying a proper tag with --format pass and format accordingly' 

test_expect_success GPG 'verifying a forged tag with --format fail and format accordingly'

test_expect_success GPG 'verifying a forged tag with --format fail and format accordingly'

  parent reply	other threads:[~2016-11-05  7:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31 21:49 What's cooking in git.git (Oct 2016, #09; Mon, 31) Junio C Hamano
2016-11-02  7:16 ` Torsten Bögershausen
2016-11-02 12:55   ` Junio C Hamano
2016-11-02  9:57 ` Johannes Schindelin
2016-11-02 12:57   ` Junio C Hamano
2016-11-02 17:04 ` Torsten Bögershausen
2016-11-02 17:40   ` Jeff King
2016-11-02 18:16     ` [PATCH 0/4] t0021 perl portability fixups Jeff King
2016-11-02 18:17       ` [PATCH 1/4] t0021: use write_script to create rot13 shell script Jeff King
2016-11-06 14:25         ` Lars Schneider
2016-11-06 14:29           ` Jeff King
2016-11-06 14:43             ` Lars Schneider
2016-11-02 18:18       ` [PATCH 2/4] t0021: put $TEST_ROOT in $PATH Jeff King
2016-11-03 20:40         ` Johannes Sixt
2016-11-03 20:44           ` Jeff King
2016-11-03 21:09             ` Johannes Sixt
2016-11-06 14:29         ` Lars Schneider
2016-11-02 18:20       ` [PATCH 3/4] t0021: use $PERL_PATH for rot13-filter.pl Jeff King
2016-11-06 14:52         ` Lars Schneider
2016-11-06 14:54           ` Jeff King
2016-11-02 18:23       ` [PATCH 4/4] t0021: fix filehandle usage on older perl Jeff King
2016-11-02 20:54         ` Torsten Bögershausen
2016-11-06 14:55         ` Lars Schneider
2016-11-02 17:43   ` What's cooking in git.git (Oct 2016, #09; Mon, 31) Johannes Sixt
2016-11-03 14:21     ` Lars Schneider
2016-11-02 17:44   ` Lars Schneider
     [not found]     ` <CAG2PGspq34wn2bAGyhR6B-XmmayadmL-v3_65y5LJWTWNHXkOQ@mail.gmail.com>
2016-11-05  7:27       ` Torsten Bögershausen
2016-11-05  7:42 ` Torsten Bögershausen [this message]
2016-11-08  8:12 ` Karthik Nayak
     [not found]   ` <CA+P7+xo+CJU_ng5OWX1y26+=QPCg6Zxpv_0opTAzsNqeFXAwng@mail.gmail.com>
2016-11-08  9:03     ` Karthik Nayak

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=20161105074231.GA15803@tb-raspi \
    --to=tboegi@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=santiago@nyu.edu \
    --cc=sunshine@sunshineco.com \
    --cc=walters@verbum.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.