From: Santiago Torres <santiago@nyu.edu>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH v5 0/6] tag: move PGP verification code to tag.c
Date: Tue, 5 Apr 2016 12:44:03 -0400 [thread overview]
Message-ID: <20160405164402.GB9507@LykOS> (raw)
In-Reply-To: <1459872449-7537-1-git-send-email-santiago@nyu.edu>
Sorry, forgot to add, this is a follow on to [1].
Thanks,
-Santiago.
[1]:
http://git.661346.n2.nabble.com/PATCH-v4-0-6-tag-move-PGP-verification-code-to-tag-c-td7652451.html
On Tue, Apr 05, 2016 at 12:07:23PM -0400, santiago@nyu.edu wrote:
> From: Santiago Torres <santiago@nyu.edu>
>
> v5 (this):
> Added helpful feedback by Eric
>
> * Reordering of the patches, to avoid temporal inclusion of a regression
> * Fix typos here and there.
> * Review commit messages, as some weren't representative of what the patches
> were doing anymore.
> * Updated t7030 to include Peff's suggestion, and added a helped-by line here
> as it was mostly Peff's code.
> * Updated the error-handling/printing issues that were introduced when.
> libifying the verify_tag function.
>
> v4:
>
> Thanks Eric, Jeff, and Hannes for the feedback.
>
> * I relocated the sigchain_push call so it comes after the error on
> gpg-interface (thanks Hannnes for catching this).
> * I updated the unit test to match the discussion on [3]. Now it generates
> the expected output of the tag on the fly for comparison. (This is just
> copy and paste from [3], but I verified that it works by breaking the
> while)
> * I split moving the code and renaming the variables into two patches so
> these are easier to review.
> * I used an adapter on builtin/tag.c instead of redefining all the fn*
> declarations everywhere. This introduces an issue with the way git tag -v
> resolves refnames though. I added a new commit to restore the previous
> behavior of git-tag. I'm not sure if I should've split this into two commits
> though.
>
> v3:
> Thanks Eric, Jeff, for the feedback.
>
> * I separated the patch in multiple sub-patches.
> * I compared the behavior of previous git tag -v and git verify-tag
> invocations to make sure the behavior is the same
> * I dropped the multi-line comment, as suggested.
> * I fixed the issue with the missing brackets in the while (this is
> now detected by the test).
>
> v2:
>
> * I moved the pgp-verification code to tag.c
> * I added extra arguments so git tag -v and git verify-tag both work
> with the same function
> * Relocated the SIGPIPE handling code in verify-tag to gpg-interface
>
> v1:
>
> The verify tag function is just a thin wrapper around the verify-tag
> command. We can avoid one fork call by doing the verification inside
> the tag builtin instead.
>
>
> This applies on v2.8.0.
>
> Thanks!
> -Santiago
>
>
> Santiago Torres (6):
> builtin/verify-tag.c: Ignore SIGPIPE on gpg-interface
> t7030-verify-tag: Adds validation for multiple tags
> builtin/verify-tag: change variable name for readability
> builtin/verify-tag: replace name argument with sha1
> builtin/verify-tag: move verification code to tag.c
> tag: use gpg_verify_function in tag -v call
>
> builtin/tag.c | 8 +------
> builtin/verify-tag.c | 65 +++++++++------------------------------------------
> gpg-interface.c | 2 ++
> t/t7030-verify-tag.sh | 12 ++++++++++
> tag.c | 48 +++++++++++++++++++++++++++++++++++++
> tag.h | 1 +
> 6 files changed, 75 insertions(+), 61 deletions(-)
>
> --
> 2.8.0
>
next prev parent reply other threads:[~2016-04-05 16:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 16:07 [PATCH v5 0/6] tag: move PGP verification code to tag.c santiago
2016-04-05 16:07 ` [PATCH v5 1/6] builtin/verify-tag.c: Ignore SIGPIPE on gpg-interface santiago
2016-04-06 16:43 ` Junio C Hamano
2016-04-05 16:07 ` [PATCH v5 2/6] t7030-verify-tag: Adds validation for multiple tags santiago
2016-04-06 6:21 ` Eric Sunshine
2016-04-17 17:31 ` Santiago Torres
2016-04-17 18:19 ` Eric Sunshine
2016-04-17 18:38 ` Santiago Torres
2016-04-17 18:53 ` Eric Sunshine
2016-04-06 16:45 ` Junio C Hamano
2016-04-05 16:07 ` [PATCH v5 3/6] builtin/verify-tag: change variable name for readability santiago
2016-04-06 16:46 ` Junio C Hamano
2016-04-05 16:07 ` [PATCH v5 4/6] builtin/verify-tag: replace name argument with sha1 santiago
2016-04-06 6:56 ` Eric Sunshine
2016-04-06 16:27 ` Junio C Hamano
2016-04-07 3:38 ` Santiago Torres
2016-04-05 16:07 ` [PATCH v5 5/6] builtin/verify-tag: move verification code to tag.c santiago
2016-04-06 16:33 ` Junio C Hamano
2016-04-05 16:07 ` [PATCH v5 6/6] tag: use gpg_verify_function in tag -v call santiago
2016-04-06 7:09 ` Eric Sunshine
2016-04-05 16:44 ` Santiago Torres [this message]
2016-04-06 7:18 ` [PATCH v5 0/6] tag: move PGP verification code to tag.c Eric Sunshine
2016-04-07 3:40 ` Santiago Torres
2016-04-07 16:19 ` Eric Sunshine
2016-04-17 17:34 ` Santiago Torres
2016-04-17 18:14 ` Eric Sunshine
2016-04-06 16:39 ` Junio C Hamano
2016-04-07 3:33 ` Santiago Torres
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=20160405164402.GB9507@LykOS \
--to=santiago@nyu.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--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 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.