From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: How to call the old repository: oe.dev or OE classic?
Date: Thu, 15 Sep 2011 17:01:09 +0100 [thread overview]
Message-ID: <1316102470.3510.0.camel@phil-desktop> (raw)
In-Reply-To: <201109151120.09382.paul.eggleton@linux.intel.com>
On Thu, 2011-09-15 at 11:20 +0100, Paul Eggleton wrote:
> 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.
Agreed. Or even "OE-legacy" or something.
p.
next prev parent reply other threads:[~2011-09-15 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 10:07 How to call the old repository: oe.dev or OE classic? Paul Menzel
2011-09-15 10:20 ` Paul Eggleton
2011-09-15 10:42 ` Koen Kooi
2011-09-15 16:01 ` Phil Blundell [this message]
2011-09-15 16:03 ` Denys Dmytriyenko
2011-09-15 15:51 ` Bernhard Guillon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1316102470.3510.0.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.