From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1a6Kf7-0000jw-1K for barebox@lists.infradead.org; Tue, 08 Dec 2015 15:58:45 +0000 Received: from weser.hi.pengutronix.de ([2001:67c:670:100:fa0f:41ff:fe58:4010]) by metis.ext.pengutronix.de with esmtp (Exim 4.80) (envelope-from ) id 1a6Kek-0007s9-3W for barebox@lists.infradead.org; Tue, 08 Dec 2015 16:58:22 +0100 Message-ID: <1449590302.3118.20.camel@pengutronix.de> From: Lucas Stach Date: Tue, 08 Dec 2015 16:58:22 +0100 Mime-Version: 1.0 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" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Messed up commit in master To: barebox@lists.infradead.org Hi Sascha, I've just stumbled across a messed up commit that landed in barebox master. It seems you squashed other unrelated commits into commit e7a8519963fcb235a123dfe5e7dd59d6fb2eaf9e (ARM: mx6sx-sabresdb: set proper hostname). I know its against the master stability rules, but I think it would be justified to split this commit properly and re-push a fixed master. Regards, Lucas -- Pengutronix e.K. | Lucas Stach | Industrial Linux Solutions | http://www.pengutronix.de/ | _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox