hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arpit Agarwal <aagar...@hortonworks.com>
Subject Re: [VOTE] reset/force push to clean up inadvertent merge commit pushed to trunk
Date Fri, 06 Jul 2018 17:24:23 GMT
-1 for the force push. Nothing is broken in trunk. The history looks ugly for two commits and
we can live with it.

The revert restored the branch to Giovanni's intent. i.e. only YARN-8435 is applied. Verified
there is no delta between hashes 0d9804d and 39ad989 (HEAD).

39ad989 2018-07-05 aengineer@ o {apache/trunk} Revert "Merge branch 't...
c163d17 2018-07-05 gifuma@apa M─┐ Merge branch 'trunk' of https://git-...
99febe7 2018-07-05 rkanter@ap │ o YARN-7451. Add missing tests to veri...
1726247 2018-07-05 haibochen@ │ o YARN-7556. Fair scheduler configurat...
0d9804d 2018-07-05 gifuma@apa o │ YARN-8435. Fix NPE when the same cli...
71df8c2 2018-07-05 nanda@apac o─┘ HDDS-212. Introduce NodeStateManager...

Regards,
Arpit


On 7/5/18, 2:37 PM, "Subru Krishnan" <subru@apache.org> wrote:

    Folks,
    
    There was a merge commit accidentally pushed to trunk, you can find the
    details in the mail thread [1].
    
    I have raised an INFRA ticket [2] to reset/force push to clean up trunk.
    
    Can we have a quick vote for INFRA sign-off to proceed as this is blocking
    all commits?
    
    Thanks,
    Subru
    
    [1]
    http://mail-archives.apache.org/mod_mbox/hadoop-yarn-dev/201807.mbox/%3CCAHqguubKBqwfUMwhtJuSD7X1Bgfro_P6FV%2BhhFhMMYRaxFsF9Q%40mail.gmail.com%3E
    [2] https://issues.apache.org/jira/browse/INFRA-16727
    

Mime
View raw message