All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Stiffler <j-stiffler@ti.com>
To: Denys Dmytriyenko <denys@ti.com>
Cc: meta-arago@arago-project.org
Subject: Re: [PATCH 1/3] packagegroup-arago-tisdk-addons: Add debug tools such as gdb
Date: Thu, 4 Feb 2016 12:53:45 -0500	[thread overview]
Message-ID: <56B39029.5040001@ti.com> (raw)
In-Reply-To: <20160204174606.GJ31480@edge>



On 2/4/2016 12:46 PM, Denys Dmytriyenko wrote:
> On Thu, Feb 04, 2016 at 12:34:16PM -0500, Jacob Stiffler wrote:
>> Can you point to where this is? I do not see any in the meta-arago
>> packagegroups, and it has been missing from our filesystem.
> images/tisdk-server-rootfs-image.bb
> packagegroups/packagegroup-arago-test-addons.bb

I'll submit a v2 with removing gdb from these locations.

> Surprisingly, server-rootfs-image is the only consumer of the test-addons
> packagegroup... And adding gdb directly to a server image was a temp hack 3+
> years ago - "nothing is more permanent than the temporary", eh? :)
>
>
>> On 2/4/2016 12:27 PM, Denys Dmytriyenko wrote:
>>> I think there are already couple places where gdb is added directly. Can we
>>> clean those up as well?
>>>



      reply	other threads:[~2016-02-04 17:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 14:04 [PATCH 1/3] packagegroup-arago-tisdk-addons: Add debug tools such as gdb Jacob Stiffler
2016-02-04 14:04 ` [PATCH 2/3] packagegroup-arago-tisdk-addons: Add ti-ipc-rtos-fw Jacob Stiffler
2016-02-04 14:04 ` [PATCH 3/3] packagegroup-arago-tisdk-addons-sdk-target: k2hk-evm: Add aif2-lld-staticdev Jacob Stiffler
2016-02-04 17:27 ` [PATCH 1/3] packagegroup-arago-tisdk-addons: Add debug tools such as gdb Denys Dmytriyenko
2016-02-04 17:34   ` Jacob Stiffler
2016-02-04 17:46     ` Denys Dmytriyenko
2016-02-04 17:53       ` Jacob Stiffler [this message]

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=56B39029.5040001@ti.com \
    --to=j-stiffler@ti.com \
    --cc=denys@ti.com \
    --cc=meta-arago@arago-project.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.