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

stevel pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/hadoop-release-support.git


 discard f512f99  HADOOP-19018. releasing
 discard 4048c78  HADOOP-19018. moving to asf-managed module
 discard 0d70a7f  HADOOP-19018. Improving design of release build file
 discard bba572e  HADOOP-19018. Improving design of release build file
 discard 29eaee8  3.4.0 RC testing
 discard df87fd0  cleanup instructions
 discard d5fe2c6  Hadoop 3.3.5 ships
 discard 9d66ad4  Hadoop 3.3.5 RC3 validation
 discard a24e295  Hadoop 3.3.5 RC3 preparation; rollback because 2 staged repos 
were created
 discard 9f8b735  Hadoop 3.3.5 RC3 preparation
 discard 062bc37  Hadoop 3.3.5 RC1
 discard a38d632  add check for api/index.html
 discard b906d3b  HADOOP-18470.  rc work
 discard cb8efc3  HADOOP-18470.  rc work
 discard 64748eb  HADOOP-18470. more work on validating the RC0
 discard ce0fb49  HADOOP-18470. releasing hadoop 3.3.5
 discard ed4f492  HADOOP-18470. releasing hadoop 3.3.5
 discard a2996a6  HADOOP-18305. 3.3.4 release work
 discard 8d97fe8  HADOOP-18305. 3.3.4 release work
 discard 6f73d84  more docs, more libraries to build, targets to invoke the 
tests
 discard 6670998  3.3.4 RC0 changes
 discard 74368d3  Add ability to download and verify source and binary dirs
 discard c29bbcb  cloudstore.build works
 discard 82dbe84  tune build.xml docs/messages
 discard 0d86cf6  cloud integration tests
 discard 0ae81cd  build hboss, spark, spark cloud integration and gcs modules.
 discard dd4a2e9  generating email message, readme, ...
 discard 94c8551  ant build file
 discard f50adf1  HADOOP-18198. update readme
 discard e466953  HADOOP-18198. Add validator project to verify that the client 
APIs work.
 discard 1404965  using java util logging
 discard 044159b  initial repo
     new 5a6fb0c  Initial repository of hadoop-release-support

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   (f512f99)
            \
             N -- N -- N   refs/heads/main (5a6fb0c)

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:


---------------------------------------------------------------------
To unsubscribe, e-mail: common-commits-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-commits-h...@hadoop.apache.org

Reply via email to