From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: How to call the old repository: oe.dev or OE classic?
Date: Thu, 15 Sep 2011 12:42:41 +0200 [thread overview]
Message-ID: <j4skr1$j8a$2@dough.gmane.org> (raw)
In-Reply-To: <201109151120.09382.paul.eggleton@linux.intel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 15-09-11 12:20, Paul Eggleton schreef:
> 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.
OEbsolete :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFOcdahMkyGM64RGpERAhgHAJ9WvlhqWWAmVJQlvUeqC4Ue6orxrACfSh09
gpzdp5Vipbbg5Znf6fca4MQ=
=31CR
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-09-15 10:55 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 [this message]
2011-09-15 16:01 ` Phil Blundell
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='j4skr1$j8a$2@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--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.