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

sergehuber pushed a change to branch UNOMI-1023-UNOMI-1024-compat-fixes
in repository https://gitbox.apache.org/repos/asf/unomi-tracker.git


 discard 6a86de0  UNOMI-1023, UNOMI-1024: Check compatibility with 1.5.0 and 
Unomi 2.3 in the server tests
 discard c40e710  UNOMI-1023, UNOMI-1024: Fix the browser build without Buffer, 
and stop sending an empty page "attributes"
    omit 34172cd  UNOMI-1019: Drop page "attributes" from the README example
    omit 48600ce  UNOMI-1019: Keep 2.0 a drop-in replacement for 1.x
    omit b3e51b8  UNOMI-1019: Add browser tests against each Unomi version
    omit bafe193  UNOMI-1019: Let the tracker send a tenant public API key
     add 5f9eba6  UNOMI-1019: Let the tracker send a tenant public API key, and 
test it against each Unomi version (#27)
     add 41bb59a  UNOMI-1023, UNOMI-1024: Fix the browser build without Buffer, 
and stop sending an empty page "attributes"
     add 9484994  UNOMI-1023, UNOMI-1024: Check compatibility with 1.5.0 and 
Unomi 2.3 in the server tests

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   (6a86de0)
            \
             N -- N -- N   refs/heads/UNOMI-1023-UNOMI-1024-compat-fixes 
(9484994)

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:

Reply via email to