From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Marek Subject: Re: linux-next: strange state of the kbuild tree Date: Tue, 08 Apr 2014 10:06:09 +0200 Message-ID: <5343ADF1.1060906@suse.cz> References: <20140408074734.34deb43270183941b5118c7f@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from cantor2.suse.de ([195.135.220.15]:54028 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756527AbaDHIGL (ORCPT ); Tue, 8 Apr 2014 04:06:11 -0400 In-Reply-To: <20140408074734.34deb43270183941b5118c7f@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org On 2014-04-07 23:47, Stephen Rothwell wrote: > Hi Michal, > > I noticed that you have two copies of two commits in your tree ("Kbuild, > lto: Set TMPDIR for LTO v4" and "Kbuild, lto: Add Link Time Optimization > support v3"). I understan why you recommitted them (to add your > Signed-off-by), but to leave the unsigned commits in there sort of > defeats the purpose. This is probably a case where you should have > removed the original merge (or just these two commits) and then merged > the new version. Sorry about that. > I am not sure what you intend to send to Linus, but this whole tree (in > one piece) should not be it. From the state of the tree, it looks like > you send your separate topic branches (or a new merge of them) which > should be ok, but please after doing that, clean up your for-next branch > (it current has merge commits dating back to May, 2103 in it). Right, I send the individual topic branches to Linus. Will it be OK if I reset the for-next branch to v3.15-rc1 after this merge window? Thanks, Michal