On Wed, Mar 30, 2011 at 12:44 PM, Peter Stuge <[email protected]> wrote: > Øyvind Harboe wrote: >> A hardware engineer that tinkers with software should be >> able to contribute without becoming a git user. > > Depends.. If they tinker with the git version of the software then > I think they *should* be a git user. > > > Tormod Volden wrote: >> letting the contributor discover the advantages of git step by step >> might be better than intimidating him with the legendary "git >> learning curve". > > In my experience the git learning curve has nothing to do with what > commands to run. Anyone can run a sequence of commands. But the > difficulties I've seen people have with git are commonly about > workflow and processes. Even if git is only used on small scale it > helps to embrace the big scale workflows. This can feel like > unneccessary overhead, and git gets the blame for it. > > I agree with a README.patches or HACKING file with brief > instructions. IMO, the important ones are: > > git config --global user.name > git config --global user.email > > while(1) { > work > git add work > git commit > } > > git pull --rebase # to catch any conflicts > git format-patch origin/master..
The above looks good to me. I like the "pull --rebase" to catch rebase problems. If these are not resolved by the submitter, then the chance that the list will work with him is a lot lower. -- Øyvind Harboe Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
