This is an automated email from the ASF dual-hosted git repository.
vy pushed a change to branch release/0.5.0
in repository https://gitbox.apache.org/repos/asf/logging-log4j-tools.git
discard 11a721a Temporarily add Apache SNAPSHOT repository
discard 38f6287 Bump `logging-parent` version to `1.10.0-SNAPSHOT`
discard a914fe5 Prepare release notes
discard f3126af Bump the version to `0.5.0`
add 7476926 Bump org.eclipse.jgit:org.eclipse.jgit (#76)
new 746a12e Bump the version to `0.5.0`
new 4a309c6 Prepare release notes
new 294efed Bump `logging-parent` version to `1.10.0-SNAPSHOT`
new 8e763dd Temporarily add Apache SNAPSHOT repository
new 71b929d Bump `logging-parent` version to `10.0.0-SNAPSHOT`
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 (11a721a)
\
N -- N -- N refs/heads/release/0.5.0 (71b929d)
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:
.github/workflows/build.yml | 4 +
RELEASING.adoc | 37 ++--
log4j-tools-parent/pom.xml | 28 ---
pom.xml | 435 +-------------------------------------------
4 files changed, 26 insertions(+), 478 deletions(-)
