This is an automated email from the ASF dual-hosted git repository.
martinzink pushed a change to branch minifi_rust_pgp
in repository https://gitbox.apache.org/repos/asf/nifi-minifi-cpp.git
discard 75e1bf9e1 refactor
discard 7c1210418 minifi_pgp set version to 1.0.0
discard dd71db68d update manifest
discard 6d413893f MINIFICPP-2749 Add EncryptContentPGP and DecryptContentPGP
add 5453f630f add anyhow error support and fold parse errors into
validation errors
add b1468a7fe MINIFICPP-2749 Add EncryptContentPGP and DecryptContentPGP
add dffcec3aa update manifest
add 3cece6df3 minifi_pgp set version to 1.0.0
add 65bc38a47 refactor
add beb4e74a8 no public key should route to failure instead of rollback
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (75e1bf9e1)
\
N -- N -- N refs/heads/minifi_rust_pgp (beb4e74a8)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../minifi_pgp/src/processors/encrypt_content.rs | 2 +-
minifi_rust/minifi_native/Cargo.toml | 1 +
minifi_rust/minifi_native/src/api/errors.rs | 85 +++++++---------------
3 files changed, 28 insertions(+), 60 deletions(-)
