I can't confirm that - there are no changes in the Gitorious repository. http://qt.gitorious.org/pyside/pyside/commits/master -- anatoly t.
On Sun, Mar 11, 2012 at 2:43 AM, paulo alcantara <[email protected]> wrote: > Maybe its better or not. It doesnt matter either. > The execellent work that Hugo has been doing (even with no much spare > time to do it) is already done. > > On 3/10/12, anatoly techtonik <[email protected]> wrote: >> On Sat, Mar 10, 2012 at 1:41 AM, Hugo Parente Lima >> <[email protected]> wrote: >>> On Friday 09 March 2012 10:14:25 Matti Airas wrote: >>>> On 09.03.2012 15:12, ext Anderson Lizardo wrote: >>>> > On Fri, Mar 9, 2012 at 8:40 AM, Matti Airas<[email protected]> >>> wrote: >>>> >> BTW, how did you actually do the removal? Did you just branch the >>>> >> repos >>>> >> before the offending commits and then merge all commits except the >>>> >> offending ones? >>>> > >>>> > I wonder if a " git rebase -i commit_id^ " (where "commit_id" is the >>>> > commit to be removed) and removing the line on the interactive rebase >>>> > editor, would fix this more or less easily :) >>>> >>>> That was the approach I tried, but that breaks down in merges. Couldn't >>>> quite figure out what the exact problem was, though. >>>> >>>> Cheers, >>>> >>>> ma. >>> >>> Work done... >> >> Just when I thought I found something.. =) >> http://linux.die.net/man/1/git-filter-branch >> >> Take a look at `git filter-branch --commit-filter`. Is it better than >> rebase? >> >> -- >> anatoly t. >> _______________________________________________ >> PySide mailing list >> [email protected] >> http://lists.qt-project.org/mailman/listinfo/pyside >> _______________________________________________ PySide mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/pyside
