This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/logback.version-1.5.3
in repository https://gitbox.apache.org/repos/asf/commons-logging.git
omit 00aa3e5 Bump logback.version from 1.3.12 to 1.5.3
add 12df6f5 Update from Logj 1 to the Log4j 2 API compatibility layer #231
add 885129a Bump log4j2.version from 2.21.1 to 2.23.1 #230
add 13b6f83 Bump ch.qos.logback:logback-classic from 1.3.12 to 1.3.14
add d467709 Bump logback.version from 1.3.12 to 1.5.3
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 (00aa3e5)
\
N -- N -- N refs/heads/dependabot/maven/logback.version-1.5.3
(d467709)
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:
src/changes/changes.xml | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
