oh boy... ;-)
was it painful?
Thanks!
On Sun, 22 Apr 2012, Tiziano Zito wrote:
Also since github PR accepted as merges, it would be best first to just
cherry pick mine on top of yours to avoid merges and then do rebase -i
done :)
--
was it painful?
not really, just a bit of vi gymnastics ;)
ciao,
tiziano
___
Pkg-ExpPsy-PyMVPA mailing list
Pkg-ExpPsy-PyMVPA@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-exppsy-pymvpa
may be some skype/shared screen
sprintee next week over remaining issues etc?
yes, if michael is around we could meet in berlin or magdeburg and
have get you on skype.
There is a bulk of changes in some guys feature branches and if we do not
merge now, later it might not be as easy ;) I
cool -- you can consider me now a contributor to this little project
;-) I have sent a pull request against your branch with few
changes, please review.
I merged your pull request, thank you :)
Also it might be nice to markup those commits which deal with python3
compatibility as PY3 (e.g.
On Sat, 21 Apr 2012, Tiziano Zito wrote:
I merged your pull request, thank you :)
glad to help ;)
that's a good idea. I fear my git foo stops at git rebase -i, to
do what you want we would need a git filter-branch, right?
I would prefer to rewrite history, if you give me a couple of hints
hi all,
with my today's efforts I got down to 13 errors and 15 failures out
of 284 tests, so it's getting better :)
on the same branch the same set of unittests passes without errors
or failures with python 2.7, so I assume I did not break anything
important.
I attach here the error logs in
thank you Tiziano!
I have started to glance over the changes -- lots of nice ones -- thanks again,
and we should finalize/merge asap - may be some skype/shared screen
sprintee next week over remaining issues etc?
There is a bulk of changes in some guys feature branches and if we do not
merge
7 matches
Mail list logo
