Jon, > My preference for handling patches would be to submit them to the Patch > tracker on Sourceforge: > > https://sourceforge.net/tracker/?group_id=128336&atid=711373 > > And then send a note to the list mentioning that the patch has been > uploaded and what it does. I will do both -- the patches normally have a description at the top, so this can be copied to the list.
Regarding patch size -- I have just converted the existing DCCP patch to match the SVN codebase. The patch is a larger monolithic chunk, the size is currently due to doing several different things: * various bugs/quirks are fixed * there is now an abstraction layer for -- connection-less vs connection-oriented transport protocols -- packet-oriented vs bytestream-oriented transport protocols, -- replacing the previous distinction between UDP/TCP -- this allows extension to other transport protocols (UDP-Lite, SCTP, ...) -- and even allows to use the same protocol in different modes * revised and verified how the client counts packets (I noted that there were several related patches already) * and (finally :), the DCCP-specific support. I am trying to make review as painless as possible and thus decided to split the larger patch into several smaller, logically separate ones. Hopefully this will make things easier. Gerrit The University of Aberdeen is a charity registered in Scotland, No SC013683. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Iperf-users mailing list Iperf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/iperf-users
