Difference between revisions of "Buildroot how to contribute"
(Created page with "A short guide, basically copy/paste from [http://lists.busybox.net/pipermail/buildroot/2010-December/039181.html mailing list]. == Configure Git == Configure your name and e-m...") |
|||
Line 1: | Line 1: | ||
A short guide, basically copy/paste from [http://lists.busybox.net/pipermail/buildroot/2010-December/039181.html mailing list]. | A short guide, basically copy/paste from [http://lists.busybox.net/pipermail/buildroot/2010-December/039181.html mailing list]. | ||
+ | |||
+ | Patches should be sent to mailing list. | ||
== Configure Git == | == Configure Git == |
Revision as of 09:34, 6 March 2012
A short guide, basically copy/paste from mailing list.
Patches should be sent to mailing list.
Configure Git
Configure your name and e-mail. This needs to be only once, if configured with --global. If you want to use some other settings for buildroot project, you first need to clone buildroot repository and then use these same commands without --global keyword.
git config --global user.name "Firstname Lastname" git config --global user.email firstname.lastname at somewhere.com
And tell git how to send emails :
git config --global sendemail.smtpserver mysmtpserver
And to avoid chained reply :
git config --global sendemail.chainreplyto false
Basic workflow
- Clone (to be done only once)
- git clone git://git.busybox.net/buildroot
- Configure Git, if not done already
- Create a branch to work on your topic (to be done for every separate topic you'd like to work with)
- git checkout -b mytopic
- Note that this also switches immediatly to the new mytopic branch. You can run 'git branch' at any time to know on which branch you are.
- git checkout -b mytopic
- Make some modifications, for one particuler subtopic (like adding the vala compiler)
- Commit those modifications
- git commit -s -a
- And enter an appropriate commit log.
- If you created new files, add them with "git add".
- And enter an appropriate commit log.
- Review your changes
- git log -p master..
- Prepare patches for your changes
- git format-patch master
- This will generate a set of 000X-*.patch files in the Buildroot directory
- git format-patch master
- Send your patches to the list
- git send-email --to buildroot at uclibc.org --compose *.patch
- All done