From: Jonathan Nieder <jrnieder@gmail.com>
To: git@vger.kernel.org
Cc: "Carlos Rica" <jasampler@gmail.com>,
"Santi Béjar" <santi@agolina.net>,
git@vger.kernel.org
Subject: [PATCH/RFC 0/5] libify verify_tag()
Date: Sat, 20 Mar 2010 00:09:54 -0500 [thread overview]
Message-ID: <20100320050953.GA24746@progeny.tock> (raw)
Hi,
I noticed that ‘git tag -v’ runs git-verify-tag (dashed form), and while
fixing that, I thought, why not make cmd_tag() run verify_tag()
directly? Here is what that would look like.
The performance impact is pretty negligible: t/t7004-tag.sh is about
2% faster after the change here (with hot or cold cache, it doesn’t
matter).
What do you think?
Jonathan Nieder (5):
tag: Run ‘git verify-tag’ using its undashed name
verify-tag: use sigchain library to block SIGPIPE
Expose verify_tag()
tag: Do not spawn a separate process for verify-tag
verify_tag_signature(): let caller look up tag object sha1
Makefile | 1 +
builtin/tag.c | 6 +--
builtin/verify-tag.c | 84 ++++------------------------------
tag.h | 2 +
builtin/verify-tag.c => verify-tag.c | 49 ++++----------------
5 files changed, 22 insertions(+), 120 deletions(-)
copy builtin/verify-tag.c => verify-tag.c (61%)
next reply other threads:[~2010-03-20 5:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-20 5:09 Jonathan Nieder [this message]
2010-03-20 5:11 ` [PATCH 1/5] tag -v: use ‘git verify-tag’ without dash Jonathan Nieder
2010-03-20 16:01 ` Johannes Sixt
2010-03-20 21:29 ` Jonathan Nieder
2010-03-20 5:12 ` [PATCH 2/5] verify-tag: use sigchain library to block SIGPIPE Jonathan Nieder
2010-03-20 5:13 ` [PATCH 3/5] Expose verify_tag() Jonathan Nieder
2010-03-20 5:14 ` [PATCH 4/5] tag -v: Do not spawn a separate process for verify-tag Jonathan Nieder
2010-03-20 22:14 ` [PATCH 4/5 v2] " Jonathan Nieder
2010-03-20 5:14 ` [PATCH 5/5] verify_tag_signature(): let caller look up tag object sha1 Jonathan Nieder
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=20100320050953.GA24746@progeny.tock \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=jasampler@gmail.com \
--cc=santi@agolina.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).