Initial GPG Signature parsing Support #3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* zoffix/fix/RT90667/Moose-enum: Fixed RT#90667
Drop this syntax as it's no longer supported[0] in 5.18. Thanks to gregor herrmann for this patch[1]! [0] http://search.cpan.org/dist/perl-5.18.0/pod/perldelta.pod#qw%28...%29_can_no_longer_be_used_as_parentheses [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711443#10
I should release more often or automate more.
Add tests for utils Update changes
This will hopefully make finding common parents of 2 given refs/tags/branches easier as well as finding if one is the parent of the other, which will be very very useful if anyone ever plans on adding a rebase function to Git::PurePerl Add tests for has_ancestor
kentfredric
force-pushed
the
gpgsig_parse
branch
from
58063dd to
c4bd5a5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the bare minimum required to get GPG Signature decoding working.
WIthout this, simply having a GPG-Signed commit in your tree will cause bad things to happen, as it fails and tries to assume the hash data is keys ...
Note that this branch is on-top-of the has_ancestor branch =).