You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by cs...@apache.org on 2022/01/12 08:49:49 UTC
[maven-resolver] branch checksums updated (09446f5 -> 8638a7c)
This is an automated email from the ASF dual-hosted git repository.
cstamas pushed a change to branch checksums
in repository https://gitbox.apache.org/repos/asf/maven-resolver.git.
discard 09446f5 Merge remote-tracking branch 'origin/master' into checksums
discard 35cf889 Add explanation
discard 0df8931 Tidy up
discard 88d656a Step more, introduce factories
discard 91e9c3b Tidy
discard e2fa3fc PR Comments
discard 9425cb8 Add UT
discard de114cc Move things in place, wire up with SL and guice
discard ede442f Checksum is not a digest
add 8638a7c [MRESOLVER-230] Make supported checksums extensible
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 (09446f5)
\
N -- N -- N refs/heads/checksums (8638a7c)
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: