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

kwin pushed a change to branch feature/leave-links-optionally-untouched
in repository https://gitbox.apache.org/repos/asf/maven-doxia.git


 discard 833864cc Optionally leave fragments of internal links untouched
     add e79bf36e Bump org.jetbrains:annotations from 26.0.2-1 to 26.1.0 (#1037)
     add 074f7843 Support strikethrough for Markdown sink (#1033)
     add 6c763e2a Optionally leave fragments of internal links untouched

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   (833864cc)
            \
             N -- N -- N   refs/heads/feature/leave-links-optionally-untouched 
(6c763e2a)

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:
 .../maven/doxia/sink/impl/AbstractSinkTest.java    | 32 +++++++++-
 .../apache/maven/doxia/module/apt/AptSinkTest.java | 12 +---
 doxia-modules/doxia-module-markdown/pom.xml        |  2 +-
 .../doxia/module/markdown/MarkdownMarkup.java      |  6 ++
 .../maven/doxia/module/markdown/MarkdownSink.java  | 71 ++++++++++++++++------
 .../doxia/module/markdown/MarkdownParserTest.java  | 13 ++++
 .../doxia/module/markdown/MarkdownSinkTest.java    |  8 +--
 .../maven/doxia/module/xdoc/XdocSinkTest.java      |  4 ++
 .../maven/doxia/module/xhtml5/Xhtml5Parser.java    |  2 +-
 .../doxia-module-xhtml5/src/site/markdown/index.md |  4 +-
 .../maven/doxia/module/xhtml5/Xhtml5SinkTest.java  | 12 +---
 11 files changed, 118 insertions(+), 48 deletions(-)

Reply via email to