This is an automated email from the ASF dual-hosted git repository.
arm pushed a change to branch moving_file_ui_to_compose
in repository https://gitbox.apache.org/repos/asf/tooling-trusted-releases.git
discard b4184e1e #931 - tidy up file planner code
add 984a55a4 #931 - tidy up file planner code
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 (b4184e1e)
\
N -- N -- N refs/heads/moving_file_ui_to_compose (984a55a4)
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:
.../{ts/move-files.ts => js/ts/move-files.js} | 447 ++++++++-------------
atr/static/js/ts/move-files.js.map | 1 +
2 files changed, 176 insertions(+), 272 deletions(-)
copy atr/static/{ts/move-files.ts => js/ts/move-files.js} (63%)
create mode 100644 atr/static/js/ts/move-files.js.map
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
