From: Junio C Hamano <gitster@pobox.com>
Date: Fri, 16 Jan 2015 22:49:46 GMT
Subject: Re: RFC: update hook for GPG signed submission on secured branches
Message-ID: <xmqq7fwm1gtx.fsf@gitster.dls.corp.google.com>
In-Reply-To: <BD3DE7B299FE458287DC8C829CEADEC2@black>

"Jason Pyeron" <jpyeron@pdinc.us> writes:

>> Is this complex pipeline the same as this (I didn't understand the
>> trailing I at the end)?
>
> Case insensitive, could have used [0-9a-fA-F].

Ahh, a GNU extension.

>> 	git cat-file commit "$newrev" |
>>         sed -ne '/^gpgsig /,/^ -----END/{
>>         	s/^gpgsig //
>>                 s/^ //p
>> 	}' |
>
> Will all future signature values end with a "^ -----END"?

If it bothers you, alternatively, you can stop at the end of the
commit object header, i.e.

	/^gpgsig /,/^$/{
        	s/^gigsig//
                s/^ //p
	}

but I do not think it matters that much ;-)