All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot SKIPS PATCHES ???
Date: Wed, 25 Apr 2012 22:52:17 +0200	[thread overview]
Message-ID: <87haw7bkla.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4F983762.2090008@petroprogram.com> ("Stefan Fröberg"'s message of "Wed, 25 Apr 2012 20:41:54 +0300")

>>>>> "Stefan" == Stefan Fr?berg <stefan.froberg@petroprogram.com> writes:


 Stefan> By the way, what is the normal process of offering new packages
 Stefan> to buildroot ?  I tried looking from buildroot pages for that
 Stefan> info but could not find it.

 Stefan> In addition to this wvstreams package I have wvdial, firefox
 Stefan> (not really an embedded system browser, but I can't live
 Stefan> without it), slim and Linux Pam packages under work.

 Stefan> Should I just offer them on buildroot mailing list for
 Stefan> reviewing or where ?

Yes, please send git-style patches to the mailing list for
review. Please also sign off on your patches (Linux kernel style) using
the -s option on git format-patch.

Once reviewed, then I'll commit the patches to git.

This is (very) shortly documented on the website:

http://buildroot.net/git.html

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2012-04-25 20:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-21 23:24 [Buildroot] Buildroot SKIPS PATCHES ??? Stefan Fröberg
2012-04-23 12:33 ` Thomas De Schampheleire
2012-04-23 13:25   ` Ludovic Desroches
     [not found]   ` <4F9586EE.9090600@petroprogram.com>
2012-04-25  5:39     ` Thomas De Schampheleire
2012-04-25 17:41       ` Stefan Fröberg
2012-04-25 20:52         ` Peter Korsgaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-04-22 13:21 Stefan Fröberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87haw7bkla.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.