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

morningman pushed a change to branch branch-1.2-lts
in repository https://gitbox.apache.org/repos/asf/doris.git


 discard 3d3cbce229 [branch1.2](deps)(aws) patch aws sdk cpp 1.9.211 (#20271)
    omit efc544e1d2 Revert "[improvement](libhdfs) Use keytab and principal to 
login kerberos (#19841)"
    omit d7574f59f3 [improvement](stacktrace) do not captute stack trace for 
txn (#19855)
    omit 0690fdc0d1 [deps](aws) upgrade to 1.9.272 to fix non-compliant RFC3986 
encoding
     new 333853045d [improvement](stacktrace) do not captute stack trace for 
txn (#19855)
     new 513babbe48 [branch1.2](deps)(aws) patch aws sdk cpp 1.9.211 (#20271)

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   (3d3cbce229)
            \
             N -- N -- N   refs/heads/branch-1.2-lts (513babbe48)

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 2 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:
 be/CMakeLists.txt          |  2 +-
 be/src/io/hdfs_builder.cpp | 34 ++++++++++++++++++++++++++++------
 thirdparty/CHANGELOG.md    |  5 -----
 thirdparty/vars.sh         |  8 ++++----
 4 files changed, 33 insertions(+), 16 deletions(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to