From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ausmtp05.au.ibm.com (ausmtp05.au.ibm.com [202.81.18.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "ausmtp05.au.ibm.com", Issuer "Equifax" (verified OK)) by ozlabs.org (Postfix) with ESMTP id C55EFDDE26 for ; Fri, 10 Aug 2007 13:07:12 +1000 (EST) Received: from d23relay03.au.ibm.com (d23relay03.au.ibm.com [202.81.18.234]) by ausmtp05.au.ibm.com (8.13.8/8.13.8) with ESMTP id l7A39DIP3506400 for ; Fri, 10 Aug 2007 13:09:14 +1000 Received: from d23av02.au.ibm.com (d23av02.au.ibm.com [9.190.250.243]) by d23relay03.au.ibm.com (8.13.8/8.13.8/NCO v8.5) with ESMTP id l7A35n8a4612278 for ; Fri, 10 Aug 2007 13:05:50 +1000 Received: from d23av02.au.ibm.com (loopback [127.0.0.1]) by d23av02.au.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l7A35nIL013159 for ; Fri, 10 Aug 2007 13:05:49 +1000 Date: Fri, 10 Aug 2007 12:59:44 +1000 From: David Gibson To: Josh Boyer Subject: Re: DTC 1.0.0 Release Coming? Message-ID: <20070810025944.GI17370@localhost.localdomain> References: <20070726030550.GA1149@localhost.localdomain> <20070726142739.GB18684@localhost.localdomain> <20070727013331.GB1561@localhost.localdomain> <20070806084813.5432ba91@weaponx.rchland.ibm.com> <20070810013001.GF17370@localhost.localdomain> <20070809203754.2e9192c5@zod.rchland.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20070809203754.2e9192c5@zod.rchland.ibm.com> Cc: linuxppc-dev@ozlabs.org, Jon Loeliger List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Aug 09, 2007 at 08:37:54PM -0500, Josh Boyer wrote: > On Fri, 10 Aug 2007 11:30:01 +1000 > David Gibson wrote: > > > > Except didn't you say you were going to work with Stephen to get DTC > > > into the kernel source itself? Keeping things similar to Kbuild might > > > help in that effort. > > > > Actually, after discussions with Stephen and Paulus, we decided not to > > take this route. In any case having Kbuild like versioning wouldn't > > actually help us any in integrating into a full Kbuild system. > > Can you elaborate why you decided not to? I'm just curious. We decided that since a formal dtc release was imminent, it would be simpler to make dtc a new kernel build requirement, rather than integrate the substantial blob of dtc code into the kernel tree and then have to deal with the maintenance / synchronization issues between the in-kernel and upstream versions. > > > > Have a look at the patch I posted. I haven't sufficiently tested it > > > > yet, but it should be able to generated version info for a tarball too > > > > (provided the .git-manifest file is included, and I'm intending that > > > > will be build by a make dist target). It will give both the > > > > git-derived based version, and a file content derived hash so we can > > > > robustly tell different builds apart, all with less code than the > > > > current system. > > > > > > That may be. But I don't see the current approach being too much of a > > > problem either. Especially given that it's already there and it > > > works. Oh, and you sent out your patch saying it wasn't ready for > > > merge and with no sign off. Small but important issues to fix I'd > > > think. > > > > Yeah, it lacks a make dist target, and needs a bit more work to > > support that properly. Never mind, I'll revisit this post the 1.0 > > release. > > Ok. > > josh > _______________________________________________ > Linuxppc-dev mailing list > Linuxppc-dev@ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-dev > -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson