This is an automated email from the ASF dual-hosted git repository.
rgupta pushed a change to branch release/1.4.0
in repository https://gitbox.apache.org/repos/asf/logging-log4j-kotlin.git
discard bc5b269 Update the `project.build.outputTimestamp` property
discard 22769f6 Remove redundant CI args
discard 362ba58 Release changelog for version `1.4.0`
discard 1d49f2b Update the `project.build.outputTimestamp` property
omit 7ab77bd Changelog for `1.4.0`
new 0e9fa8d Changelog for `1.4.0`
new 47c0423 Update the `project.build.outputTimestamp` property
new 6e2c00c Release changelog for version `1.4.0`
new 62a434b Remove redundant CI args
new 841a6d1 Update the `project.build.outputTimestamp` property
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 (bc5b269)
\
N -- N -- N refs/heads/release/1.4.0 (841a6d1)
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.
The 5 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
