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

zhangduo pushed a change to branch HBASE-30004
in repository https://gitbox.apache.org/repos/asf/hbase.git


 discard e498de6ba49 fix
 discard cc5d95f0c7a fix
 discard f4230eacc56 fix
 discard f53ee4604cf fix
 discard b1728807666 fix
 discard 598083a157d fix
 discard 855df802568 fix
 discard 4196fbf98f4 fix
 discard 2db1526b202 add permission
 discard a10828c9422 fix
 discard d3a611531b1 HBASE-30004 Implement a new generate web site jenkins job
     new 9e52cfbb6d3 HBASE-30004 Implement a new generate web site jenkins job

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   (e498de6ba49)
            \
             N -- N -- N   refs/heads/HBASE-30004 (9e52cfbb6d3)

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 1 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:
 dev-support/generate-website/generate-hbase-website.Jenkinsfile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Reply via email to