From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758687Ab3EOMZp (ORCPT ); Wed, 15 May 2013 08:25:45 -0400 Received: from cantor2.suse.de ([195.135.220.15]:56378 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754535Ab3EOMZn (ORCPT ); Wed, 15 May 2013 08:25:43 -0400 Message-ID: <51937EC2.6050604@suse.cz> Date: Wed, 15 May 2013 14:25:38 +0200 From: Michal Marek User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: linux-next: comment on the kbuild tree References: <20130515092505.294f3a8865c77e8420d27491@canb.auug.org.au> In-Reply-To: <20130515092505.294f3a8865c77e8420d27491@canb.auug.org.au> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 15.5.2013 01:25, Stephen Rothwell wrote: > Hi Michal, > > Since the kbuild tree now consists only of merge commits (relative to > v3.10-rc1), you might as well just reset it to v3.10-rc1 and have a nice > clean tree to start from. I thought I would newer rebase the for-next branch to allow people to pull from it. But I can see that it looks much cleaner in the linux-next tree if you can do a git log stable..master and see what is really in linux-next. So I reset it to v3.10-rc1 now. Michal