This is an automated email from the ASF dual-hosted git repository.
yiconghuang pushed a change to branch refactor/move-amber-under-texera
in repository https://gitbox.apache.org/repos/asf/texera.git
discard 356a0200bf fix: format
discard b0bb4405dc chore: move apache.amber to apache.texera.amber
add ea428050e6 refactor: move amber package from org.apache.amber to
org.apache.texera.amber
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 (356a0200bf)
\
N -- N -- N refs/heads/refactor/move-amber-under-texera
(ea428050e6)
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:
