sweetlilmre/android-async-http — pull request #1 by mkuprionis (2013-01-23 12:32:46+00:00)
Title: Recent changes at original repo working with refactored response handlers

Hi,

I must say I didn't really test this, only made changes for compiler to pass. But then there's no big reason for this not to work.

Now, these changes are rather small. But if you checked my commits on `md` branch, you'd see there's some more serious stuff there. And here I'm a bit confused on how to carry on with this:

Your pull request at @loopj repo introduces braking changes - I just went through refactoring to make my app work with your refactored code. However I love work you've done there and will continue building on that base.

And here is the problem - for instance, I've done some good work on request cancellation. That's fairly fresh code, but I'm actively working on this and will probably fine tune the solution. So I'm building on your refactored base, but have code which would be useful at original codebase as well. And I'm not eager too much to port the changes to non-refactored / original codebase. Question is, where should I put my contributions?

If I make pull requests to your repo that's basically a different fork and would potentially fragment the community effort.

So what do you think about this? Would you like me to make pull requests to you when I have some new stuff?