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

sunzesong pushed a change to branch jira_550
in repository https://gitbox.apache.org/repos/asf/incubator-iotdb.git.


 discard 23564eb  Merge remote-tracking branch 'upstream/master' into jira_545
 discard 299865b  [IOTDB-550] Fix TSMRWriteExample executes unsuccessfully
    omit 7c35b55  Merge remote-tracking branch 'upstream/master' into jira_545
    omit 60ba663  [IOTDB-545] Update checkPathValidity in Session
    omit cbf5fe0  Add header
    omit f3eb4bb  Add UT
    omit 2c4d81e  Fix tests
    omit 3a36b36  Fix code smell
    omit a51e48c  Separate matcher to nodes
    omit 84b7135  [IOTDB-545] Update checkPathValidity in Session
     add 8437710  [IOTDB-545] Update checkPathValidity in Session

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   (23564eb)
            \
             N -- N -- N   refs/heads/jira_550 (8437710)

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