On May 14, 2012, at 4:18 PM, Andrei - Constantin Popescu wrote: > However I don't know if I can achieve the commit access before coding begins. > Can it be achieved in a shorter period of time (provided the patches number > is acceptable by Brl-cad community)? What should I do?
There are a number of you that either have patches pending review or haven't yet otherwise submitted a patches allowing you to have commit access. For those that haven't submitted at least a couple patches, that is obviously your top priority as the coding window begins. For those that have submitted a patch and haven't received feedback, you should certainly begin working on your project, but you'll have to do so in small incremental patch form. Work as if you had commit access, but instead of "svn commit", you'll run "svn diff" and post the output to the patch tracker. Be sure to respond to any feedback. Usually the process will only take a day or two if there are no problems. > I have read the mail regarding the libkpg packages larger than 24k causing > issues. I have attempted to transfer packages with content from /dev/random > up to size 30k , it seemed to work fine. Is a specific file type that causes > the issue. The issue isn't the size or type of file, but the buffer size of the libpkg packages being transferred. You'll have to modify code to test that. As I mentioned earlier, I suggest making the buffer size an option to tpkg instead of using the hard-coded 2048 buffer size. Cheers! Sean ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
