Buildroot how to contribute

From eLinux.org
Revision as of 16:29, 6 March 2012 by Roland (Talk | contribs) (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...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

A short guide, basically copy/paste from 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

  1. Clone (to be done only once)
  2. Configure Git, if not done already
  3. 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.
  4. Make some modifications, for one particuler subtopic (like adding the vala compiler)
  5. Commit those modifications
  6. git commit -s -a
    • And enter an appropriate commit log.
      • If you created new files, add them with "git add".
  7. Review your changes
    • git log -p master..
  8. Prepare patches for your changes
    • git format-patch master
      • This will generate a set of 000X-*.patch files in the Buildroot directory
  9. Send your patches to the list
    • git send-email --to buildroot at uclibc.org --compose *.patch
  10. All done