All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: openembedded-devel@lists.openembedded.org
Cc: Koen Kooi <koen@dominion.thruhere.net>,
	Martin Jansa <martin.jansa@gmail.com>,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-kde][PATCH 3/3] README: update contributor list
Date: Thu, 7 Mar 2013 15:05:16 +0000	[thread overview]
Message-ID: <CAJTo0LbnE7DjdJL=9=LDA3kpxhAADJONAu-4Xdwohcno__xXcA@mail.gmail.com> (raw)
In-Reply-To: <5138A92D.5030809@balister.org>

On 7 March 2013 14:50, Philip Balister <philip@balister.org> wrote:
>> For me, codenames work fine but for users it is sometimes confusing as
>> the website and marketing people talk about Yocto 1.3 or 1.4 while the
>> involved people talk about codenames. So I find myself explaining it
>> over and over again.
>
> Add me to the list of people that find codenames confusing. I can't
> reliably list releases in order by name.

We really need a table on the wiki page listing all of them - I can
easily remember the current/previous/next names but after that I don't
remember them.

Ross



  reply	other threads:[~2013-03-07 15:22 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
2013-03-07 14:41           ` Otavio Salvador
2013-03-07 14:50             ` Philip Balister
2013-03-07 15:05               ` Burton, Ross [this message]
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='CAJTo0LbnE7DjdJL=9=LDA3kpxhAADJONAu-4Xdwohcno__xXcA@mail.gmail.com' \
    --to=ross.burton@intel.com \
    --cc=koen@dominion.thruhere.net \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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.