From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga09.intel.com ([134.134.136.24]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1TJOC3-0008HM-2I for openembedded-devel@lists.openembedded.org; Wed, 03 Oct 2012 14:36:51 +0200 Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 03 Oct 2012 05:23:32 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.80,527,1344236400"; d="scan'208";a="201031437" Received: from unknown (HELO helios.localnet) ([10.252.122.52]) by orsmga001.jf.intel.com with ESMTP; 03 Oct 2012 05:23:44 -0700 From: Paul Eggleton To: Koen Kooi Date: Wed, 03 Oct 2012 13:23:43 +0100 Message-ID: <1396458.ob1fernpZs@helios> Organization: Intel Corporation User-Agent: KMail/4.9.1 (Linux/3.2.0-31-generic-pae; KDE/4.9.1; i686; ; ) In-Reply-To: References: <2386446.3zWsEst4ZG@helios> MIME-Version: 1.0 Cc: "openembedded-devel@lists.openembedded.org" Subject: Re: [meta-webserver][PATCH 0/6] Add meta-webserver X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2012 12:36:51 -0000 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" On Wednesday 03 October 2012 13:43:30 Koen Kooi wrote: > Op 3 okt. 2012, om 13:29 heeft Paul Eggleton het volgende geschreven: > > On Wednesday 03 October 2012 13:27:41 Koen Kooi wrote: > >> Op 3 okt. 2012 om 12:43 heeft Paul Eggleton > >> > > > > het volgende geschreven: > >>> On Wednesday 03 October 2012 12:24:19 Koen Kooi wrote: > >>>> Squash those "import" with the "fix" commits, no sense in having a > >>>> broken > >>>> recipe in there. > >>> > >>> I'd rather not - there is sense in being clear about the changes, > >>> because > >>> there are a large number of them in this case. > >> > >> The broken recipes are still available in OE classic if people want to > >> compare them. I still don't get why you want to have broken recipes in > >> the > >> tree at multiple points in your series. > > > > Because I want to easily see in "git blame" where particular lines came > > from - did I add them, or have they been around for ages? > > Does oe-core have the same flow for new recipes? You already know the answer to this. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre