Jason Pyeron schrieb am 16.01.2015 um 21:05:
-Original Message-
From: Junio C Hamano
Sent: Friday, January 16, 2015 14:53
Jonathan Nieder jrnie...@gmail.com writes:
would there be interest in accepting a patch for
%Gs - the raw GPG text from the commit
%Gf - the key fingerprint
I can't agree that
COMMITID=ef8df950c8d16dace62e55d18b26617b1268f1bc; \
git cat-file $COMMITID -p |\
sed -e '/^ /{H;$!d;}; x;/^gpgsig /!d; s/^gpgsig//;' |\
cut -c 2- |\
gpg --list-packets --textmode |\
sed '/keyid/!d; s/.*keyid \([0-9A-F]\{16\}\).*/\1/I'
is the way to go, when
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
Jonathan Nieder jrnie...@gmail.com writes:
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. ;-)
I was about to say As long as
-Original Message-
From: Junio C Hamano
Sent: Friday, January 16, 2015 14:53
Jonathan Nieder jrnie...@gmail.com writes:
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
5 matches
Mail list logo
