[maven-resolver] branch checksums updated (e28ef77 -> bcf66e4)

[cs...@apache.org]

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 e28ef77  Fix SL and Guice
 discard d7122f2  ChecksumUtils dismantle, pt 3
 discard d9493cd  ChecksumUtils dismantle, pt 2
 discard 3f14c5c  Phase out ChecksumUtils
 discard 7d14527  More tidy
 discard 5d08c3b  Tidy
 discard 8b597a7  Smaller fixes, drop unused
 discard 8638a7c  [MRESOLVER-230] Make supported checksums extensible
     add bcf66e4  [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   (e28ef77)
            \
             N -- N -- N   refs/heads/checksums (bcf66e4)

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: