This is an automated email from the ASF dual-hosted git repository.
bmarwell pushed a change to branch MRESOLVER-382_outgoing_interface
in repository https://gitbox.apache.org/repos/asf/maven-resolver.git
discard 20dc2fd6 [MRESOLVER-382] rephrase exception to reflect behaviour change
discard 8400efa8 [MRESOLVER-382] rename method to reflect behaviour change
discard b6075383 [MRESOLVER-382] throw exception on error to fail the build.
discard fcbcf794 [MRESOLVER-382] use var name 'address' everywhere
discard 1b93469a [MRESOLVER-382] extract method b/c of checkstyle method length
discard d5b556ac [MRESOLVER-382] implement optional bind address
add 59e1c169 [MRESOLVER-382] implement optional bind address
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 (20dc2fd6)
\
N -- N -- N refs/heads/MRESOLVER-382_outgoing_interface
(59e1c169)
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:
