[ambari-logsearch] branch cloudbreak updated (f40991f -> 5670040)

[ol...@apache.org]

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

oleewere pushed a change to branch cloudbreak
in repository https://gitbox.apache.org/repos/asf/ambari-logsearch.git.


 discard f40991f  Merge pull request #5 from tobias-istvan/AMBARI-24551-master
    omit 75c120d  [AMBARI-24551] [Log Search UI] get rid of redundant requests after undoing or redoing several history steps - PR change requests
    omit 20c27ea  [AMBARI-24551] [Log Search UI] get rid of redundant requests after undoing or redoing several history steps - cleaning up the branch, writing tests fixing issues revealed by unit tests.
    omit 5df64b3  [AMBARI-24551] [Log Search UI] get rid of redundant requests after undoing or redoing several history steps - fixing dropdown with icons, optimize code readibility, changing labels
    omit bc2b995  [AMBARI-24551] [Log Search UI] get rid of redundant requests after undoing or redoing several history steps - request in progress indicators
    omit 12fc1b7  [AMBARI-24551] [Log Search UI] get rid of redundant requests after undoing or redoing several history steps - working history manager
    omit 1990a75  [AMBARI-24551] [Log Search UI] get rid of redundant requests after undoing or redoing several history steps - change history manager with actions/reducers/effects focused solution.
    omit 30c3157  [AMBARI-24551] [Log Search UI] get rid of redundant requests after undoing or redoing several history steps - fixing form control implementations
    omit 2c14a70  In progress
    omit dcadc20  [AMBARI-24551] [Log Search UI] get rid of redundant requests after undoing or redoing several history steps - PR fixes
    omit d09e5c3  [AMBARI-24551] [Log Search UI] get rid of redundant requests after undoing or redoing several history steps
     add 5670040  [AMBARI-24551] [Log Search UI] get rid of redundant requests after undoing or redoing several history steps (#22)

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   (f40991f)
            \
             N -- N -- N   refs/heads/cloudbreak (5670040)

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: