git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Santiago Torres <santiago@nyu.edu>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH/RFC] builtin/tag: Changes argument format for verify
Date: Sat, 27 Feb 2016 13:31:33 -0500	[thread overview]
Message-ID: <20160227183133.GB12822@sigill.intra.peff.net> (raw)
In-Reply-To: <20160227174523.GB11593@LykOS>

On Sat, Feb 27, 2016 at 12:45:24PM -0500, Santiago Torres wrote:

> > A much more interesting change in this area, I think, would be to skip
> > verify-tag entirely. Once upon a time it had a lot of logic itself, but
> > these days it is a thin wrapper over run_gpg_verify(), and we could
> > improve the efficiency quite a bit by eliminates the sub-process
> > entirely.
> 
> I agree here too. while going through gdb to follow the logic on this I saw that
> this code forks three times (git, tag-verify and gpg). I'm sure that
> removing one layer should be good efficiencly-wise.
> 
> Is it ok if I give this a shot?

Sure.

I suspect the extra process is there for historical reasons; git-tag was
originally a shell script that called out to git-verify-tag, and the
conversion to C retained the separate call.

I cannot think of a reason that it would be a bad thing to do it all in
a single process. Do note the trickery with SIGPIPE in verify-tag,
though. We probably need to do the same here (in fact, I wonder if that
should be pushed down into the code that calls gpg).

-Peff

  reply	other threads:[~2016-02-27 18:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27  0:27 [PATCH/RFC] builtin/tag: Changes argument format for verify santiago
2016-02-27  4:36 ` Jeff King
2016-02-27 17:45   ` Santiago Torres
2016-02-27 18:31     ` Jeff King [this message]
2016-03-03 22:05       ` Santiago Torres
2016-03-03 22:26         ` 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=20160227183133.GB12822@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=santiago@nyu.edu \
    /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).