[Buildroot] How do patches get committed?

[Buildroot] How do patches get committed?

[Matthew Bastian]

This week I submitted some patches for RTAI realtime. I presume that 
just because I submitted them that they are not automatically 
incorporated into the latest release.

So who vets these and how can I make sure my patches get incorporated?

Matt

[Buildroot] How do patches get committed?

[Samuel Martin]

Hi Matthew,

On Thu, Feb 26, 2015 at 2:23 PM, Matthew Bastian
<Matthew.Bastian@nrc-cnrc.gc.ca> wrote:
> This week I submitted some patches for RTAI realtime. I presume that just
> because I submitted them that they are not automatically incorporated into
> the latest release.

Here is a few answers [1,2] how the Buildroot project works and
patches get applied.

Don't worry, your patches are not lost. ;-) Just give some time to
reviewers/testers/maintainers to process the patch backlog [3]. As you
can see, there is a bit more than 300 patches in the pipes, and we
tend to process them in a fifo way. ;-)

Anyway, helping the community to process patches is very much
appreciated :-) You can find how to help here [4].

[1] http://lists.busybox.net/pipermail/buildroot/2013-February/066902.html
[2] http://lists.busybox.net/pipermail/buildroot/2013-February/066927.html
[3] http://patchwork.ozlabs.org/project/buildroot/list/
[4] http://nightly.buildroot.org/#_contributing_to_buildroot
>
> So who vets these and how can I make sure my patches get incorporated?
>
> Matt
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

Regards,

-- 
Samuel

[Buildroot] How do patches get committed?

[Peter Korsgaard]

>>>>> "Samuel" == Samuel Martin <s.martin49@gmail.com> writes:

 > Hi Matthew,
 > On Thu, Feb 26, 2015 at 2:23 PM, Matthew Bastian
 > <Matthew.Bastian@nrc-cnrc.gc.ca> wrote:
 >> This week I submitted some patches for RTAI realtime. I presume that just
 >> because I submitted them that they are not automatically incorporated into
 >> the latest release.

 > Here is a few answers [1,2] how the Buildroot project works and
 > patches get applied.

 > Don't worry, your patches are not lost. ;-) Just give some time to
 > reviewers/testers/maintainers to process the patch backlog [3]. As you
 > can see, there is a bit more than 300 patches in the pipes, and we
 > tend to process them in a fifo way. ;-)

 > Anyway, helping the community to process patches is very much
 > appreciated :-) You can find how to help here [4].

Exactly. On top of that we are also very close to releasing v2015.02, so
focus is on stabilization and not new features (for the master branch)
right now.

-- 
Bye, Peter Korsgaard