This is an automated email from the ASF dual-hosted git repository.
yasith pushed a change to branch feat/svclayer-portal
in repository https://gitbox.apache.org/repos/asf/airavata.git
discard 0a24f600cb feat(portal): add Next.js frontend application
discard 51ba2e25a8 feat: migrate to REST API, remove Thrift, and clean up
legacy
discard 0e93213a4d feat: add Spring Boot service layer architecture
discard 29538a569c feat(db): add schema migrations, Flyway baseline, and DB
init scripts
add 7d0d8fb1a9 feat(db): unify all databases into single airavata DB with
schema migrations (#592)
add f7e41da466 feat: add Spring Boot service layer architecture
add ae3d2bed44 feat: migrate to REST API, remove Thrift, and clean up
legacy
new 2c07ed0560 feat(portal): add Next.js frontend application
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 (0a24f600cb)
\
N -- N -- N refs/heads/feat/svclayer-portal (2c07ed0560)
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:
