From: Santiago Torres <santiago@nyu.edu>
To: git@vger.kernel.org
Cc: gitster@pobox.com, peff@peff.net, sunshine@sunshineco.com,
walters@verbum.org
Subject: Re: [PATCH v4 0/7] Add --format to tag verification
Date: Tue, 11 Oct 2016 13:43:49 -0400 [thread overview]
Message-ID: <20161011174349.dp44e4ir6tweuzzv@LykOS.localdomain> (raw)
In-Reply-To: <20161007210721.20437-1-santiago@nyu.edu>
[-- Attachment #1: Type: text/plain, Size: 2504 bytes --]
Hi,
I noticed there were no replies for this thread. I was curious if it got
buried because I sent it on the Friday evening before a long weekend.
I don't mean to pressure or anything.
Thanks!
-Santiago.
On Fri, Oct 07, 2016 at 05:07:14PM -0400, santiago@nyu.edu wrote:
> From: Santiago Torres <santiago@nyu.edu>
>
> This is the fourth iteration of the series in [1][2][3], which comes as a
> result of the discussion in [4]. The main goal of this patch series is to bring
> --format to git tag verification so that upper-layer tools can inspect the
> content of a tag and make decisions based on those contents.
>
> In this re-woll we:
>
> * Fixed the author fields and signed off by's throughout the patch
> series
>
> * Added two more patches with unit tests to ensure the format specifier
> behaves as expected
>
> * Fixed a missing initialization for the format specifier in verify-tag which
> caused a crash.
>
> * Fixed an outdated git commit message that had the previous name of a
> function definition.
>
> Thanks,
> -Santiago
>
> [1] http://public-inbox.org/git/20160930221806.3398-1-santiago@nyu.edu/
> [2] http://public-inbox.org/git/20160922185317.349-1-santiago@nyu.edu/
> [3] http://public-inbox.org/git/20160926224233.32702-1-santiago@nyu.edu/
> [4] http://public-inbox.org/git/20160607195608.16643-1-santiago@nyu.edu/
>
>
> Lukas Puehringer (4):
> tag: add format specifier to gpg_verify_tag
> gpg-interface, tag: add GPG_VERIFY_QUIET flag
> ref-filter: add function to print single ref_array_item
> builtin/tag: add --format argument for tag -v
>
> Santiago Torres (3):
> builtin/verify-tag: add --format to verify-tag
> t/t7030-verify-tag: Add --format specifier tests
> t/t7004-tag: Add --format specifier tests
>
> Documentation/git-tag.txt | 2 +-
> Documentation/git-verify-tag.txt | 2 +-
> builtin/tag.c | 34 +++++++++++++++++++++++-----------
> builtin/verify-tag.c | 13 +++++++++++--
> gpg-interface.h | 1 +
> ref-filter.c | 10 ++++++++++
> ref-filter.h | 3 +++
> t/t7004-tag.sh | 16 ++++++++++++++++
> t/t7030-verify-tag.sh | 16 ++++++++++++++++
> tag.c | 22 +++++++++++++++-------
> tag.h | 4 ++--
> 11 files changed, 99 insertions(+), 24 deletions(-)
>
> --
> 2.10.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2016-10-11 17:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 21:07 [PATCH v4 0/7] Add --format to tag verification santiago
2016-10-07 21:07 ` [PATCH v4 1/7] gpg-interface, tag: add GPG_VERIFY_QUIET flag santiago
2016-10-19 8:51 ` Jeff King
2016-10-07 21:07 ` [PATCH v4 2/7] ref-filter: add function to print single ref_array_item santiago
2016-10-19 8:55 ` Jeff King
2016-10-19 9:16 ` Jeff King
2016-10-19 17:07 ` Santiago Torres
2016-10-19 20:35 ` Jeff King
2016-10-19 20:35 ` [PATCH 1/2] ref-filter: split ref_kind_from_filter Jeff King
2016-10-19 21:23 ` Junio C Hamano
2016-10-19 21:33 ` Jeff King
2016-10-19 20:39 ` [PATCH 2/2] tag: send fully qualified refnames to verify_tag_and_format Jeff King
2016-10-20 16:57 ` Santiago Torres
2016-10-20 21:39 ` Jeff King
2016-10-07 21:07 ` [PATCH v4 3/7] tag: add format specifier to gpg_verify_tag santiago
2016-10-07 21:07 ` [PATCH v4 4/7] builtin/verify-tag: add --format to verify-tag santiago
2016-10-19 9:04 ` Jeff King
2016-10-07 21:07 ` [PATCH v4 5/7] builtin/tag: add --format argument for tag -v santiago
2016-10-19 9:10 ` Jeff King
2016-10-07 21:07 ` [PATCH v4 6/7] t/t7030-verify-tag: Add --format specifier tests santiago
2016-10-19 9:13 ` Jeff King
2016-10-07 21:07 ` [PATCH v4 7/7] t/t7004-tag: " santiago
2016-10-11 17:43 ` Santiago Torres [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161011174349.dp44e4ir6tweuzzv@LykOS.localdomain \
--to=santiago@nyu.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).