This is an automated email from the ASF dual-hosted git repository.
cstamas pushed a change to branch file-lock
in repository https://gitbox.apache.org/repos/asf/maven-resolver.git.
discard 2f69359 [MRESOLVER-219] File advisory locking based NamedLocks
add 6760f2a Remove unused class
add d134522 [MRESOLVER-219] File advisory locking based NamedLocks
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 (2f69359)
\
N -- N -- N refs/heads/file-lock (d134522)
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:
