This is an automated email from the ASF dual-hosted git repository.

michaelo pushed a change to branch doxia-2.0.0
in repository https://gitbox.apache.org/repos/asf/maven-pmd-plugin.git


 discard cda51dd  [MPMD-390] Dynamically calculate xrefLocation/xrefTestLocation
 discard 4ec6e72  [MPMD-389] Upgrade to Doxia 2.0.0 Milestone Stack
     add c9b1c5d  (doc) Update release notes for 3.23.0 and 3.24.0 (#161)
     add f4ca739  [MPMD-400] (doc) Fix doc URL for PMD 7.3.0 (#160)
     add 8a76263  Minor copy edit (#162)
     add 749a34a  [MPMD-389] Upgrade to Doxia 2.0.0 Milestone Stack
     add 737a0e5  [MPMD-390] Dynamically calculate xrefLocation/xrefTestLocation

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   (cda51dd)
            \
             N -- N -- N   refs/heads/doxia-2.0.0 (737a0e5)

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:
 pom.xml                                            |  4 +--
 src/site/apt/examples/cpdCsharp.apt.vm             |  6 ++--
 .../apt/examples/upgrading-PMD-at-runtime.apt.vm   |  2 +-
 src/site/markdown/releasenotes.md                  | 40 ++++++++++++++++++++--
 4 files changed, 44 insertions(+), 8 deletions(-)

Reply via email to