All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Mills <wmills@ti.com>
To: "Maupin, Chase" <chase.maupin@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [PATCH 1/3] matrix-gui-browser: port from arago overlay
Date: Fri, 27 Jan 2012 15:42:56 -0500	[thread overview]
Message-ID: <4F230C50.8070400@ti.com> (raw)
In-Reply-To: <7D46E86EC0A8354091174257B2FED1010BF9D9FE@DLEE12.ent.ti.com>


On 01/27/2012 03:39 PM, Maupin, Chase wrote:
>>
>> -----Original Message-----
>> From: Denys Dmytriyenko [mailto:denis@denix.org]
>> As of today's state of Arago - if you don't count recipes/ti, which
>> was
>> "untouchable" for some special reasons, everything else is quite
>> clean with
>> using amends everywhere possible! And our of all the people you
>> should know
>> this better.
> There are plenty of recipes in arago outside of the ti directory that are not just amends.  What I am saying is that I would like to split the bbappends into their own directory so that we can more easily track what we are appending and ideally find ways to drive those changes into lower common layers (not that we always can)
>

So it can be even clearer and cleaner than it is today.  Great.  Sounds 
like a good task for a meta-arago owner.




  reply	other threads:[~2012-01-27 20:42 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 ` [PATCH 1/3] matrix-gui-browser: port from arago overlay William Mills
2012-01-27 11:50   ` 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 [this message]
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=4F230C50.8070400@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.