From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vms173001pub.verizon.net ([206.46.173.1]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1R4EV2-0002H7-OU for openembedded-devel@lists.openembedded.org; Thu, 15 Sep 2011 18:09:16 +0200 Received: from gandalf.denix.org ([unknown] [71.191.138.237]) by vms173001.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LRK002ALNA5KPUB@vms173001.mailsrvcs.net> for openembedded-devel@lists.openembedded.org; Thu, 15 Sep 2011 11:03:54 -0500 (CDT) Received: by gandalf.denix.org (Postfix, from userid 1000) id D795414AF5F; Thu, 15 Sep 2011 12:03:41 -0400 (EDT) Date: Thu, 15 Sep 2011 12:03:41 -0400 From: Denys Dmytriyenko To: openembedded-devel@lists.openembedded.org Message-id: <20110915160341.GA24402@denix.org> References: <1316081269.4523.54.camel@mattotaupa> <201109151120.09382.paul.eggleton@linux.intel.com> MIME-version: 1.0 In-reply-to: <201109151120.09382.paul.eggleton@linux.intel.com> User-Agent: Mutt/1.5.16 (2007-06-09) Subject: Re: How to call the old repository: oe.dev or OE classic? 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: Thu, 15 Sep 2011 16:09:16 -0000 Content-type: text/plain; charset=us-ascii Content-disposition: inline On Thu, Sep 15, 2011 at 11:20:09AM +0100, Paul Eggleton wrote: > On Thursday 15 September 2011 11:07:48 Paul Menzel wrote: > > it is confusing for outsiders if oe.dev and OE classic are referring to > > the same repository or not. > > I can see how people could be confused, so yes we probably ought to have just > one name. > > > So we need to make up an official name for the old repository. oe.dev or > > OE classic? I favor oe.dev, because it is shorter > > oe-dev/oe.dev being a shortened "org.openembedded.dev" is kind of a relic of > the old (was it bitkeeper or monotone?) days prior to git. The benefit of > "classic" is it draws attention to the fact that it's deprecated, whereas to > me, dev implies that's where development still occurs. So my personal vote is > for OE-classic. Seems like "OE classic" is already becoming a de-facto standard among developers... -- Denys