From: Jonathan Nieder <jrnieder@gmail.com>
To: Jason Pyeron <jpyeron@pdinc.us>
Cc: git@vger.kernel.org
Subject: Re: Proper plumbing for porcelain gpg formats on git show?
Date: Fri, 16 Jan 2015 11:29:47 -0800 [thread overview]
Message-ID: <20150116192947.GD29365@google.com> (raw)
In-Reply-To: <EB979B4B153D49909C78239A333869FB@black>
Hi,
Jason Pyeron wrote:
> COMMITID=ef8df950c8d16dace62e55d18b26617b1268f1bc; \
> git show $COMMITID --pretty=format:%GK -s
>
> do the same thing.
>
> Is there a way to properly extract the GPG signature object, such
> that GPG operations may be done on it?
>
> Are the git log formats safe to use in scripts (asking because it
> was said not to use at
> http://git.661346.n2.nabble.com/show-pretty-B-without-a-diff-td5852061.html#a5853270)?
Better to use
git diff-tree -s --always --format=%GK $COMMITID
[...]
> would there be interest in accepting a patch for
>
> %Gs - the raw GPG text from the commit
> %Gf - the key fingerprint
There may be bikeshedding on the exact format specifier, but aside
from that I don't see why not. ;-)
Thanks,
Jonathan
next prev parent reply other threads:[~2015-01-16 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 16:57 Proper plumbing for porcelain gpg formats on git show? Jason Pyeron
2015-01-16 19:29 ` Jonathan Nieder [this message]
2015-01-16 19:52 ` Junio C Hamano
2015-01-16 20:05 ` Jason Pyeron
2015-01-19 14:13 ` Michael J Gruber
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=20150116192947.GD29365@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=jpyeron@pdinc.us \
/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).