On Mar 24, 2011, at 3:30 AM, Paul Ivanov <pivanov...@gmail.com> wrote:
> I offer my sincerest apologies, I royally screwed up and thought > that I was pushing out to one of my own branches and somehow > ended up pushing a 2 day old copy of master out to > matplotlib/master with 'git push -f'. Assuming Mike's work from > today is also in his own master branch, I think the damage can be > undone by just pulling from > https://github.com/mdboom/matplotlib/master and pushing that to > https://matplotlib/matplotlib/master, but at this point I don't > trust myself and just want to not cause any more damage than I've > already done. > > I realize that people get their commit right revoked for such > careless shenanigans, but I will be grateful if you'd all allow > me the opportunity always run any push commands with the > --dry-run flag from now on. With git you can clean up bad commits by simply changing the reference to master, or reorder and edit commits with rebase. Darren, can you take a look and see what should be done? It may be more complicated when you have multiple forks and branches, this part I'm less clear on so perhaps Darren you can comment on this too. Anyhow Paul, just an accident. Pales in comparison to my losing all of the ancient commit history in a CVS reorganization. > ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
