On Wed, Mar 30, 2011 at 6:53 AM, Øyvind Harboe wrote: > These are great suggestions. Do you know of anyone who's written > such readmes in GPL projects that we could copy?
Googling (readme.patches "git commit") gave some examples: http://git-scm.com/ http://git.savannah.gnu.org/cgit/gnutls.git/tree/README http://www.dragonflybsd.org/docs/developer/TypicalGitUsage/ On Wed, Mar 30, 2011 at 9:46 AM, Øyvind Harboe wrote: > I think the big challenge is how to put the user on the right > path and reward him with small successes early on. If we don't want to scare anyone away with a lot of git commands, just let new contributors get away with: git clone... (do hacking) git diff (to review their changes) git diff > patch (attach the patch to a normal mail) Then the next time he has a patch, encourage the use of "git commit -a" and "git format-patch", then the next time again "git send-email" which can be more work to set up, depending on mail provider/ISP/etc. I find git helpful at any level, even if you don't do the full "correct" procedure as Luca wrote up. So letting the contributor discover the advantages of git step by step might be better than intimidating him with the legendary "git learning curve". OTOH I don't really think anyone getting their hands dirty with openocd internals can be scared away by the clear instructions that Luca wrote :) Tormod _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
