mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: how to get my patch to master or barebox dev cycle
Date: Wed, 3 Nov 2010 23:08:58 +0100	[thread overview]
Message-ID: <20101103220858.GJ6017@pengutronix.de> (raw)
In-Reply-To: <AANLkTimYPa2XDhv4HsL6U0eK-csu4dGqiNeu2BUcLwEv@mail.gmail.com>

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

      reply	other threads:[~2010-11-03 22:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03 19:46 Belisko Marek
2010-11-03 22:08 ` Sascha Hauer [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=20101103220858.GJ6017@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=marek.belisko@gmail.com \
    /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