mail archive of the barebox mailing list
 help / color / mirror / Atom feed
* how to get my patch to master or barebox dev cycle
@ 2010-11-03 19:46 Belisko Marek
  2010-11-03 22:08 ` Sascha Hauer
  0 siblings, 1 reply; 2+ messages in thread
From: Belisko Marek @ 2010-11-03 19:46 UTC (permalink / raw)
  To: barebox

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: how to get my patch to master or barebox dev cycle
  2010-11-03 19:46 how to get my patch to master or barebox dev cycle Belisko Marek
@ 2010-11-03 22:08 ` Sascha Hauer
  0 siblings, 0 replies; 2+ messages in thread
From: Sascha Hauer @ 2010-11-03 22:08 UTC (permalink / raw)
  To: Belisko Marek; +Cc: barebox

Hi Marek,

On Wed, Nov 03, 2010 at 08:46:25PM +0100, Belisko Marek wrote:
> 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?

I maintain two branches, master and next. next is always open to new
patches. After a (monthly) release I merge the next branch into master.
The master branch only gets fixes for collateral damages caused by
merging the next branch.
In case of the mini2440 patch I simply forgot to handle it, sorry for
that. I will have a look at it tomorrow.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-11-03 22:09 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-11-03 19:46 how to get my patch to master or barebox dev cycle Belisko Marek
2010-11-03 22:08 ` Sascha Hauer

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox