This is an automated email from the ASF dual-hosted git repository.
carlosrovira pushed a change to branch feature/vivid-ui-set
in repository https://gitbox.apache.org/repos/asf/royale-asjs.git.
discard d9038f1 Merge branch 'develop' into feature/vivid-ui-set
discard ecaab75 fresh branch with all vivid work, still not work
add bda2745 Added md extension to RELEASE_NOTES
add 6a9c949 Added build status badge
add df64863 The badge should point to lastSuccessfulBuild
add e480b70 Added RELEASE_NOTES.md to Ant RAT check
new 9832117 fresh branch with all vivid work, still not work
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 (d9038f1)
\
N -- N -- N refs/heads/feature/vivid-ui-set (9832117)
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 1 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:
README.md | 1 +
RELEASE_NOTES => RELEASE_NOTES.md | 0
build.xml | 1 +
pom.xml | 2 ++
4 files changed, 4 insertions(+)
rename RELEASE_NOTES => RELEASE_NOTES.md (100%)
--
To stop receiving notification emails like this one, please contact
[email protected].
