From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-devel@lists.openembedded.org,
Martin Jansa <martin.jansa@gmail.com>
Subject: Re: [meta-kde][PATCH 3/3] README: update contributor list
Date: Thu, 07 Mar 2013 14:35:06 +0000 [thread overview]
Message-ID: <9088096.rvOOlWx1VE@helios> (raw)
In-Reply-To: <E780D109-3D15-488F-8CC9-F6829BEE90F1@dominion.thruhere.net>
On Thursday 07 March 2013 15:03:17 Koen Kooi wrote:
> Op 7 mrt. 2013, om 14:04 heeft Martin Jansa <martin.jansa@gmail.com> het
> volgende geschreven:
> > It would be nice to know yocto-1.4 release name in advance and name it
> > the same as branch in oe-core/meta-oe will be (denzil, danny, ...), but
> > I guess it can be renamed later.
>
> For angstrom I'm going to use 'yocto-1.4' in the branch name, I have trouble
> remembering which names maps to which release. And the Yocto compliance
> program talks about 1.3, .14 etc, not about codenames.
Wouldn't it be worth us trying to standardise rather than all doing our own
thing and users having to figure out what matches up between different layers?
If others feel the same as you, then maybe we should all be using that schema.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-03-07 14:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 9:50 [meta-kde][PATCH 1/3] packagegroup-kde-apps: remove multiline comment Koen Kooi
2013-03-07 9:50 ` [meta-kde][PATCH 2/3] ark, gwenview: fix RDEPENDS Koen Kooi
2013-03-07 9:50 ` [meta-kde][PATCH 3/3] README: update contributor list Koen Kooi
2013-03-07 12:09 ` Samuel Stirtzel
2013-03-07 13:04 ` Martin Jansa
2013-03-07 14:03 ` Koen Kooi
2013-03-07 14:35 ` Paul Eggleton [this message]
2013-03-07 14:41 ` Otavio Salvador
2013-03-07 14:50 ` Philip Balister
2013-03-07 15:05 ` Burton, Ross
2013-03-07 15:15 ` Burton, Ross
2013-03-07 15:18 ` Koen Kooi
2013-03-07 15:24 ` Richard Purdie
2013-03-07 15:41 ` Paul Eggleton
2013-03-11 12:34 ` Peter A. Bigot
2013-03-07 14:52 ` Martin Jansa
2013-03-07 15:30 ` Richard Purdie
2013-03-07 13:10 ` Paul Eggleton
2013-03-07 14:04 ` Samuel Stirtzel
2013-03-07 15:05 ` Martin Jansa
2013-03-07 15:20 ` Samuel Stirtzel
2013-03-07 15:56 ` Martin Jansa
2013-03-20 12:14 ` Samuel Stirtzel
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=9088096.rvOOlWx1VE@helios \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=martin.jansa@gmail.com \
--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.