From: Matthew Bastian <Matthew.Bastian@nrc-cnrc.gc.ca>
To: buildroot@busybox.net
Subject: [Buildroot] How do patches get committed?
Date: Thu, 26 Feb 2015 08:23:55 -0500 [thread overview]
Message-ID: <54EF1E6B.8060100@nrc-cnrc.gc.ca> (raw)
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
next reply other threads:[~2015-02-26 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 13:23 Matthew Bastian [this message]
2015-02-26 14:24 ` [Buildroot] How do patches get committed? Samuel Martin
2015-02-26 22:22 ` Peter Korsgaard
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=54EF1E6B.8060100@nrc-cnrc.gc.ca \
--to=matthew.bastian@nrc-cnrc.gc.ca \
--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