From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from plane.gmane.org ([80.91.229.3]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1RzbcX-0005gC-Nh for ptxdist@pengutronix.de; Mon, 20 Feb 2012 23:22:11 +0100 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1RzbcW-0007C6-82 for ptxdist@pengutronix.de; Mon, 20 Feb 2012 23:22:08 +0100 Received: from h96-60-251-119.cncrtn.dsl.dynamic.tds.net ([96.60.251.119]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 20 Feb 2012 23:22:08 +0100 Received: from jkirk865 by h96-60-251-119.cncrtn.dsl.dynamic.tds.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 20 Feb 2012 23:22:08 +0100 From: Jerry Kirk Date: Mon, 20 Feb 2012 22:21:57 +0000 (UTC) Message-ID: Mime-Version: 1.0 Subject: [ptxdist] Advice on Directory Structure Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de I'm looking for some advice on how to structure the source code directories of our new embedded linux project that will rely on PTXDist. Our development will run the full breadth including new drivers, patches to existing drivers, applications, etc. I've been reviewing the "practical project workspace" outlined in O'Reilly's Building Embedded Linux Systems book. It's a fair start but not as detailed as I had hoped. We're using some sort of cloud based DVCS system for sourc code controla s well. Any advice would be great to try and avoid painful restructures. -- ptxdist mailing list ptxdist@pengutronix.de