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

rombert pushed a change to branch feature/SLING-7605
in repository https://gitbox.apache.org/repos/asf/sling-ide-tooling.git.


 discard da3891b  SLING-7605 - ContentDeploymentTest sometimes fails on Jenkins
 discard eaa2cde  SLING-8287 - DirWatcherTest consistently fails on Jenkins
 discard 6cdcf63  SLING-8287 - DirWatcherTest consistently fails on Jenkins
 discard 6aca254  SLING-8287 - DirWatcherTest consistently fails on Jenkins
 discard 3b0bcae  SLING-8287 -  DirWatcherTest consistently fails on Jenkins
 discard 915c4a3  SLING-7605 - ContentDeploymentTest sometimes fails on Jenkins
     new e5184fd  SLING-7605 - ContentDeploymentTest sometimes fails on Jenkins
     new c3466a8  SLING-8287 -  DirWatcherTest consistently fails on Jenkins

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   (da3891b)
            \
             N -- N -- N   refs/heads/feature/SLING-7605 (c3466a8)

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 802 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:

Reply via email to