All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Mills <wmills@ti.com>
To: Chase Maupin <Chase.Maupin@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH 1/3] matrix-gui-browser: port from arago overlay
Date: Thu, 26 Jan 2012 17:44:05 -0500	[thread overview]
Message-ID: <4F21D735.5000303@ti.com> (raw)
In-Reply-To: <1327603585-5599-1-git-send-email-Chase.Maupin@ti.com>

On 01/26/2012 01:46 PM, Chase Maupin wrote:
> * This package adds a simple web browser GUI application with
>    no decorations used to display matrix on the local display.
> * Ported from arago overlay
>

Sorry for hijacking your patch Chase but I have serious big picture 
questions about all this stuff going into meta-ti and especially all 
into one layer.

meta-ti is suppose to be the TI specific stuff people need to support 
their platforms regardless of what layer stack they are using.  I 
understand we are not layer stack independent yet but that needs to be 
the goal.  Certainly adding a whole bunch of non-HW related stuff into 
the same layer is not going to move us any closer.

When we talked about where matrix belonged before there was debate about 
meta-oe or meta-arago.  When did I miss the memo that put it into meta-ti??



  parent reply	other threads:[~2012-01-26 22:44 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 18:46 [PATCH 1/3] matrix-gui-browser: port from arago overlay Chase Maupin
2012-01-26 18:46 ` [PATCH 2/3] refresh-screen: add package from arago Chase Maupin
2012-01-26 18:46 ` [PATCH 3/3] matrix-gui: update to latest version Chase Maupin
2012-01-26 22:44 ` William Mills [this message]
2012-01-27 11:50   ` [PATCH 1/3] matrix-gui-browser: port from arago overlay Koen Kooi
2012-01-27 12:09     ` Andreas Müller
2012-01-27 12:24       ` Koen Kooi
2012-01-27 17:38         ` William Mills
2012-01-27 19:39         ` Denys Dmytriyenko
2012-01-27 19:47           ` Koen Kooi
2012-01-27 20:09             ` Denys Dmytriyenko
2012-01-27 13:50     ` Maupin, Chase
2012-01-27 14:54       ` Philip Balister
2012-01-27 15:19         ` Maupin, Chase
2012-01-27 17:51       ` William Mills
2012-01-27 19:46         ` Maupin, Chase
2012-01-27 20:03           ` William Mills
2012-01-27 20:05             ` William Mills
2012-01-27 20:10             ` Tom Rini
2012-01-27 20:11               ` Denys Dmytriyenko
2012-01-27 20:19                 ` Philip Balister
2012-01-27 20:24                   ` Denys Dmytriyenko
2012-01-27 20:20                 ` William Mills
2012-01-27 20:11           ` William Mills
2012-01-27 20:17             ` Maupin, Chase
2012-01-27 20:21               ` Denys Dmytriyenko
2012-01-27 20:24                 ` William Mills
2012-01-27 20:29                   ` Maupin, Chase
2012-01-27 20:34                     ` Denys Dmytriyenko
2012-01-27 20:39                       ` Maupin, Chase
2012-01-27 20:42                         ` William Mills
2012-01-27 20:44                           ` Maupin, Chase
2012-01-27 20:48                             ` William Mills
2012-01-27 20:34                     ` William Mills
2012-01-27 20:50                   ` Philip Balister
2012-01-27 20:54                     ` Koen Kooi
2012-01-27 20:57                     ` Denys Dmytriyenko
2012-01-27 22:40                       ` Philip Balister
2012-01-27 23:39                         ` Denys Dmytriyenko
2012-01-27 20:53                 ` Koen Kooi
2012-01-27 20:55                   ` Maupin, Chase
2012-01-27 21:52                     ` William Mills
2012-01-27 23:04                       ` Koen Kooi
2012-01-28  3:23                         ` Philip Balister
2012-01-27 17:30     ` William Mills

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=4F21D735.5000303@ti.com \
    --to=wmills@ti.com \
    --cc=Chase.Maupin@ti.com \
    --cc=meta-ti@yoctoproject.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.