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

jiangphcn pushed a change to branch sm52
in repository

 discard 9ed61e6  Fixup: address seal()
 discard 61bf28b  address seal() and require() issues
 discard 697f8ab  upgrade SM to 60
     add b6ed038  upgrade SM to 60

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   (9ed61e6)
             N -- N -- N   refs/heads/sm52 (b6ed038)

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:
 test/javascript/tests/view_sandboxing.js | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

Reply via email to