Skip to content

Conversation

@cevich
Copy link
Contributor

@cevich cevich commented Sep 16, 2020

Fixes #46

When using git log, if some/all commits are gpg-signed, git will
automatically try to validate the signatures by default. This results
in printing additional text. This additional gpg-validation text is
then incorrectly interpreted by git-validate as if they were commit
IDs. Fix the problem by using the rev-list sub-command which will
ONLY list the IDs.

Signed-off-by: Chris Evich cevich@redhat.com

When using `git log`, if some/all commits are gpg-signed, git will
automatically try to validate the signatures by default.  This results
in printing additional text.  This additional gpg-validation text is
then incorrectly interpreted by `git-validate` as if they were commit
IDs.  Fix the problem by using the `rev-list` sub-command which will
ONLY list the IDs.

Signed-off-by: Chris Evich <cevich@redhat.com>
Copy link
Owner

@vbatts vbatts left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

largely LGTM.
comparing the output of these two commands locally looks like there is a final newline, but I don't think that'll be an issue. Let's find out ;-)

@vbatts vbatts merged commit 60cb871 into vbatts:master Sep 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

git-validation barfs on gpg signature verification output of git log

2 participants