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 209081e Merge remote-tracking branch 'origin/master' into file-lock
discard 4d17426 Merge remote-tracking branch 'origin/master' into file-lock
omit ef890d7 Undo "experiment"
omit fd3f558 Merge remote-tracking branch 'origin/master' into file-lock
omit 3f517b7 Refactor and make config integration friendly.
omit e70f09c Bugfix: FS lock had bug to detect "is any other thread has
lock"
omit 4cf8a1c Experiment: make file locks default
omit 3a86f55 Enroll file stuff in module
omit 81bd541 Update doco
omit 7030b51 File Locking change proposal
omit f70f44d Format
omit 54b565e Add new bits to selector, add doco
omit 2d51102 FS locks did "finish" before given time passed
omit c695a72 Make allowed diff broader
omit 1791fe5 Do not give up too early
omit b532816 Add name mapper usable with file lock
omit 29e14e6 Add session aware FileLockNamedLockFactory
omit 16eb043 File advisory locking based NamedLocks
add 2f69359 [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 (209081e)
\
N -- N -- N refs/heads/file-lock (2f69359)
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:
