BinaryFunction and DoubleDoubleFunction shouldn't be changed (there isn't much there to change anyway).
What did you need to change? BinaryFunction just extends DDF in any case. Splitting a diff can be done by simply editing the diff by hand. That is probably easiest. If you use git, then you can commit small changes locally and then rearrange the commits to your liking and generate separate diffs for each change. With IntelliJ, you can use the local history to generate diffs between any two points in time. That doesn't give you quite as much power as with git, but it is very useful. With SVN, hand-editing the patch is probably the best tactic. We can help get things cleaned up. On Fri, Aug 6, 2010 at 12:16 PM, <[email protected]> wrote: > a.) I was also working with getting Mahout Math to work with Solr-trunk and > carrot-3.4-dev trunk. Consequently, I also have changes that add > DoubleFunctions; replacing Binary and Unary Functions in places. I do not > know what the state of IntFunction, IntIntFunction, vs BinaryFunction and > UnaryFunction in Mahout-dev, but on my machine I added a set of classes for > DoubleFunction, DoubleDoubleFunction, and DoubleComparator. I changed files > to reference these new classes, rather than Binary and Unary. Do you which > should be used - Double or Binary/Unary? I will comb through my changed > files to separate the two feature changes on my machine - is there a way to > separate out files from a diff file (I have already generated one).
