From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from 8bytes.org ([85.214.48.195]:48398 "EHLO mail.8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932237Ab3CGLHC (ORCPT ); Thu, 7 Mar 2013 06:07:02 -0500 Received: from localhost (localhost [127.0.0.1]) by mail.8bytes.org (Postfix) with SMTP id A2A4B12B087 for ; Thu, 7 Mar 2013 12:07:00 +0100 (CET) Date: Thu, 7 Mar 2013 12:06:59 +0100 From: Joerg Roedel Subject: Re: [PATCH] buildtar: Add ARCH to the archive name Message-ID: <20130307110659.GC22602@8bytes.org> References: <1362557147-14393-1-git-send-email-bp@alien8.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1362557147-14393-1-git-send-email-bp@alien8.de> Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Borislav Petkov Cc: Michal Marek , linux-kbuild@vger.kernel.org, LKML , Borislav Petkov On Wed, Mar 06, 2013 at 09:05:47AM +0100, Borislav Petkov wrote: > From: Borislav Petkov > > When dealing with multiple sub-arches (like 32- and 64-bit on x86, for > example) generating a bunch of kernel tar archives with the same name > but for different sub-arches could get confusing and error-prone. Also, > the build process could overwrite otherwise unrelated builds and you > probably don't want that. So, add the architecture to the archive name > for more clarity and less shoot-yourself-in-the-foot practices. > > Signed-off-by: Borislav Petkov Good idea, but I already hear people yelling about their scripts that break with this change :) Joerg