From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] how do I contribute to buildroot
Date: Wed, 6 Jun 2012 22:13:30 +0200 [thread overview]
Message-ID: <20120606221330.283ad2cf@skate> (raw)
In-Reply-To: <1338989304.528.YahooMailNeo@web171306.mail.ir2.yahoo.com>
Hello Vincent,
Le Wed, 6 Jun 2012 14:28:24 +0100 (BST),
Vincent de RIBOU <vins_bozo@yahoo.fr> a ?crit :
> Let me introduce myself.
> I am a long term user of buildroot since 2009-08.
> I am working on decoder/STB buildroot based products for a leader in france.
Welcome!
> I had not really contribute until now to buildroot in committing changes and relevant custom configs.
>
> How do I contribute and have access to push request on Git repo??
> Is it possible??
> Is it reserved to short list committers??
> Am I intended to do patches to be committed by others??
Buildroot works just like the Linux kernel and many other open-source
projects: a single maintainer has write access to the official Git
repositories.
Contributors, even long term contributors, must post patches on the
list, or send pull requests to the maintainer. Patches posted to the
list are preferred since it allows everybody to contribute to the
review and testing effort.
From an introduction on how to contribute to Buildroot, you can have a
look at http://elinux.org/Buildroot_how_to_contribute.
If you have questions, do not hesitate to ask on this list or on the
IRC channel.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-06-06 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 13:28 [Buildroot] how do I contribute to buildroot Vincent de RIBOU
2012-06-06 20:13 ` Thomas Petazzoni [this message]
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=20120606221330.283ad2cf@skate \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox