From: Belisko Marek <marek.belisko@gmail.com>
To: barebox@lists.infradead.org
Subject: how to get my patch to master or barebox dev cycle
Date: Wed, 3 Nov 2010 20:46:25 +0100 [thread overview]
Message-ID: <AANLkTimYPa2XDhv4HsL6U0eK-csu4dGqiNeu2BUcLwEv@mail.gmail.com> (raw)
Hi,
today I get an announce about new v2010.11.0 and I try to look to
commits if my patch which was sent 19.10
for mini2440 board support
(http://lists.infradead.org/pipermail/barebox/2010-October/001881.html
) was taken.
Patch was commented only to add some extra functionality and I suppose
it could be taken to
next branch and then to master in next release. But it was not.
So my question is what is development cycle for barebox? Similar to
kernel with merge window and then only release?
Thanks for clarification.
Best Regards,
marek
--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer
Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
icq: 290551086
web: http://open-nandra.com
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2010-11-03 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 19:46 Belisko Marek [this message]
2010-11-03 22:08 ` Sascha Hauer
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=AANLkTimYPa2XDhv4HsL6U0eK-csu4dGqiNeu2BUcLwEv@mail.gmail.com \
--to=marek.belisko@gmail.com \
--cc=barebox@lists.infradead.org \
/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