[ODE] patches/unstable etc...

[Rodrigo Hernandez]

I just added your patch to UNSTABLE,
diff patches are usually ok, I dont think there are set rules as to how 
you should
submit patches, the issue with not applying patches is more of not 
having time to test and make
sure the patch does what is supposed to do than how a patch should be 
submited, I think.

Cheers!

Jaroslav Sinecky wrote:

>Hi all!
>I know this is an old topic but I just still don't get how the patches are
>working. There have been couple of patches on the maillist that seem to be
>very useful (or least worth trying). As far as I understood the unstable
>branch in CVS was created for these kind of stuff, but I don't see any of
>these patches in the CVS UNSTABLE. Even for example the "position-correcting
>constraints" patch by Adam Moss that appeared in April is not there.
>So if I want to try some of these patches I should apply them using the
>textual difference format that you guys attach to mails? How? Manualy or is
>there some utility for this?
>And if let's say I have a bugfix, what should I do? Create a diff w.r.t.
>current CVS head and send it to the list?
>
>The fact is I have a bug fix ... see this thread
>http://q12.org/pipermail/ode/2005-June/016060.html. I cleaned and optimized
>bit the code and added joint feedback printout functionality to
>test_boxstack, so one can see clearly that what the original code returns is
>completly wrong (feedbacks summed from all joints for each body) and the new
>at least appears to be correct.
>I think this could save time and nerves to someone else, so if someone could
>answer my questions, I would appreciate it very much.
>
>Jaroslav
>
>
>
>
>_______________________________________________
>ODE mailing list
>ODE at q12.org
>http://q12.org/mailman/listinfo/ode
>  
>