Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] How do patches get committed?
Date: Thu, 26 Feb 2015 23:22:29 +0100	[thread overview]
Message-ID: <87r3tc48ka.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAHXCMMLaQA9RTWxPv3mRmCd5E2oArRVakcnExajxLYFrm1mi8Q@mail.gmail.com> (Samuel Martin's message of "Thu, 26 Feb 2015 15:24:36 +0100")

>>>>> "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

      reply	other threads:[~2015-02-26 22:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 13:23 [Buildroot] How do patches get committed? Matthew Bastian
2015-02-26 14:24 ` Samuel Martin
2015-02-26 22:22   ` Peter Korsgaard [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=87r3tc48ka.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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