This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel.git.
omit 6c88dcb Regen for commit 0f420786ffecdbc37274232495d4c0f86e0cac67
add d57e7f3 camel-salesforce: Support Bulk jobs via Bulk 2.0 API
add 8e10cab Regen for commit d57e7f3165091c28a7b46f5ca96f73deb9d53037
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 (6c88dcb)
\
N -- N -- N refs/heads/regen_bot (8e10cab)
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:
.../apache/camel/component/salesforce/api/dto/bulkv2/JobStateEnum.java | 2 ++
1 file changed, 2 insertions(+)
