From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-yw0-f49.google.com ([209.85.213.49]) by canuck.infradead.org with esmtp (Exim 4.72 #1 (Red Hat Linux)) id 1PDjHx-0005Nu-4j for barebox@lists.infradead.org; Wed, 03 Nov 2010 19:46:30 +0000 Received: by ywg8 with SMTP id 8so813871ywg.36 for ; Wed, 03 Nov 2010 12:46:26 -0700 (PDT) MIME-Version: 1.0 Date: Wed, 3 Nov 2010 20:46:25 +0100 Message-ID: From: Belisko Marek List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: barebox-bounces@lists.infradead.org Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: how to get my patch to master or barebox dev cycle To: barebox@lists.infradead.org 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