http://forums.leaflabs.com/topic.php?id=707 A place to share, learn, and grow... en-US Fri, 22 Jan 2016 00:13:02 +0000 http://bbpress.org/?v=1.0.2 q http://forums.leaflabs.com/search.php http://forums.leaflabs.com/topic.php?id=707#post-5237 Wed, 15 Jun 2011 03:27:50 +0000 mbolivar 5237@http://forums.leaflabs.com/ <p>well, this has been part of the official docs for a while now, so i'm unsticking. </p> http://forums.leaflabs.com/topic.php?id=707#post-4140 Mon, 04 Apr 2011 15:59:07 +0000 mbolivar 4140@http://forums.leaflabs.com/ <p>Adam,</p> <p>Sorry if I came off brusque in my previous, no offense was meant.</p> <p>It does make sense to formalize the patch submission procedure. I've added an FAQ about it to the libmaple design doc; it'll get incorporated (in some form) into the next release:</p> <p><a href="http://static.leaflabs.com/mbolivar/libmaple_design/faq.html#how-can-i-help-commit-patches" rel="nofollow">http://static.leaflabs.com/mbolivar/libmaple_design/faq.html#how-can-i-help-commit-patches</a></p> <p>Update: making this topic sticky until the official docs include this information. </p> http://forums.leaflabs.com/topic.php?id=707#post-4106 Thu, 31 Mar 2011 21:27:40 +0000 Adam 4106@http://forums.leaflabs.com/ <p>Marti,</p> <p>I just meant, "If my instructions are wrong, will you correct (improve) them?" That's all - I didn't mean to improve the process. It seems pretty easy to follow, I the steps I laid out are ok. </p> http://forums.leaflabs.com/topic.php?id=707#post-4104 Thu, 31 Mar 2011 12:52:13 +0000 mbolivar 4104@http://forums.leaflabs.com/ <p>Adam,</p> <p>Yup, github pull requests are ideal. If you're super allergic to git for some reason, I suppose you could email us patches at <a href="mailto:info@leaflabs.com">info@leaflabs.com</a>, but that's a lot less convenient.</p> <p>Not sure what you mean by "improve this"; I'm extremely impressed with the convenience github has provided thus far.</p> <p>UweBonnes,</p> <p>A _lot_ has happened since 0.0.9. All of our development work is currently taking place against the "refactor" branch in the libmaple github repository. Patches to the low-level pure C code will almost certainly not apply. We're grateful for your patches, but would encourage you to work against the current development code if you're going to be contributing patches for the time being.</p> <p>The refactor branch has a preliminary design document here:</p> <p><a href="http://static.leaflabs.com/mbolivar/libmaple_design/" rel="nofollow">http://static.leaflabs.com/mbolivar/libmaple_design/</a></p> <p>In particular, the hard-coded clk_speed (along with the rest of usart.h and usart.c) have been largely rewritten to be more general. I have yet to push those changes (they're in my local clone), but am hoping to get them in by the end of the week. </p> http://forums.leaflabs.com/topic.php?id=707#post-4095 Wed, 30 Mar 2011 13:56:37 +0000 Adam 4095@http://forums.leaflabs.com/ <p>I am not a Leaf Labs employee- but here is my take on how to do this:</p> <p>1. Create a github account <a href="http://github.com" rel="nofollow">http://github.com</a><br /> 2. Fork the Leaf Labs project you want to contribute to - git hub makes this easy: <a href="https://github.com/leaflabs" rel="nofollow">https://github.com/leaflabs</a><br /> 3. Clone the forked git repository.<br /> 4. Make your modifications and commit them to your local repository.<br /> 5. Push the changes back to your forked repo on github.<br /> 6. Issue a pull request via github and contact Leaf Labs staff via the Forums.</p> <p>Leaf Labs people, will you improve this? </p> http://forums.leaflabs.com/topic.php?id=707#post-4093 Wed, 30 Mar 2011 13:26:27 +0000 UweBonnes 4093@http://forums.leaflabs.com/ <p>How to contribute/RFC patches? This forums seems not to allow uploads. A mail address would be preferred. I have to patches pending:<br /> - A small one removing the hard coded values in usart.c for "clk_speed"<br /> - A larger one with (hopefully) all those changes discussed in the STM32 Discovery thread.</p> <p>The changes are against maple-ide-0.0.9-linux64.tgz. I unpacked in a "git init" directory. </p>