This is an automated email from the ASF dual-hosted git repository.
pkarwasz pushed a change to branch fix/2.x/2937-http-watcher
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
omit aab9235cfd Merge remote-tracking branch 'apache/2.24.x' into
fix/2.x/2937-http-watcher
omit 9a3b1c114a Add comment before listeners call
omit e8cabb32f4 Comment out nullability annotation due to JDK bug
omit 7acd8b6af8 Try workaround JDK bug again
omit d5f95eb7ce Backport workaround of JDK-8152174
omit ca6e232895 Fix BND failures
omit 35973f73ac Single constructor for `ConfigurationSource`
omit ed1eac5957 Improve log message
omit cf73143ebd Fix reloading of the configuration from HTTP(S)
add 421d8a797f Revert "Fix reloading of the configuration from HTTP(S)"
add 2e4d0a81db Fix reloading of the configuration from HTTP(S)
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 (aab9235cfd)
\
N -- N -- N refs/heads/fix/2.x/2937-http-watcher (2e4d0a81db)
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:
