You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Jake Farrell (JIRA)" <ji...@apache.org> on 2014/04/26 07:15:15 UTC

[jira] [Updated] (INFRA-7631) Need to reset Bigtop repo's master HEAD due to an accidental merge

     [ https://issues.apache.org/jira/browse/INFRA-7631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jake Farrell updated INFRA-7631:
--------------------------------

    Status: Waiting for user  (was: Waiting for Infra)

We typically do not allow resetting history for something like this. You can revert the commits with the following 

git revert 5171af3
git revert 6adc1d9 -m 2
git push origin master


> Need to reset Bigtop repo's master HEAD due to an accidental merge
> ------------------------------------------------------------------
>
>                 Key: INFRA-7631
>                 URL: https://issues.apache.org/jira/browse/INFRA-7631
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Git
>         Environment: bigtop git repository at
>   http://git-wip-us.apache.org/repos/asf/bigtop.git
>            Reporter: Konstantin Boudnik
>
> I have messed up the master branch on Bigtop git repo. The correct master is currently pushed to branch {{master.fixed}}. We need to make the {{master}} be equivalent to the head of {{master.fixed}} branch. Any chance the force-push ban can be lifted for 5 minutes on this repository, so I can reset it properly? 
> Otherwise, can anyone with sufficient privileges to do this for us?



--
This message was sent by Atlassian JIRA
(v6.2#6252)