[Openocd-development] Untested or slightly tested code

2011-05-25 Thread j. m. norris
Would it make sense for those individuals who are submitting code that is untested or slightly tested to include a short write-up on their setup? This write-up would allow those with a little free time on their hands or for someone who wants to learn about the development involved with OpenOCD

Re: [Openocd-development] Untested or slightly tested code

2011-05-25 Thread Øyvind Harboe
On Wed, May 25, 2011 at 1:33 PM, j. m. norris jmnor...@ieee.org wrote: Would it make sense for those individuals who are submitting code that is untested or slightly tested to include a short write-up on their setup? This write-up would allow those with a little free time on their hands or

Re: [Openocd-development] Untested or slightly tested code

2011-05-25 Thread Rodrigo Rosa
should the short write-up go in the email with the corresponding patch? On Wed, May 25, 2011 at 4:40 AM, Øyvind Harboe oyvind.har...@zylin.com wrote: On Wed, May 25, 2011 at 1:33 PM, j. m. norris jmnor...@ieee.org wrote: Would it make sense for those individuals who are submitting code

Re: [Openocd-development] Untested or slightly tested code

2011-05-25 Thread Øyvind Harboe
On Wed, May 25, 2011 at 7:43 PM, Rodrigo Rosa rodrigorosa...@gmail.com wrote: should the short write-up go in the email with the corresponding patch? I think splitting out the docs in a separate patch is just fine. -- Øyvind Harboe Can Zylin Consulting help on your project? US toll free