From: "Martin Ertsås" <mertsas@cisco.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] rootfs_ipk, image: Add debug capture support
Date: Tue, 02 Oct 2012 15:52:21 +0200 [thread overview]
Message-ID: <506AF195.9040008@cisco.com> (raw)
In-Reply-To: <CAP9ODKp3H99BCS3k0K890Eb6xtM2_8Toph4T2=Q1yNvZK5XeLQ@mail.gmail.com>
On 10/02/12 15:53, Otavio Salvador wrote:
> On Tue, Oct 2, 2012 at 10:51 AM, Phil Blundell <philb@gnu.org> wrote:
>> On Tue, 2012-10-02 at 10:42 -0300, Otavio Salvador wrote:
>>> Or IMAGE_FEATURES += "dbg-img" ;-)
>> Where is that implemented? I couldn't find any obvious reference to
>> dbg-img in any classes.
> Sorry by cause a missunderstanding ... I was just pointing to a
> possible new feature you could add.
>
that feature is already implemented though, in dbg-pkgs. If you don't
mean dbg-img should do something other/more than what dbg-pkgs does?
- Martin
next prev parent reply other threads:[~2012-10-02 14:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 9:20 [PATCH] rootfs_ipk, image: Add debug capture support Phil Blundell
2012-10-02 11:12 ` Richard Purdie
2012-10-02 11:15 ` Phil Blundell
2012-10-02 11:38 ` Richard Purdie
2012-10-02 13:42 ` Otavio Salvador
2012-10-02 13:51 ` Phil Blundell
2012-10-02 13:53 ` Otavio Salvador
2012-10-02 13:52 ` Martin Ertsås [this message]
2012-10-02 13:59 ` Otavio Salvador
2012-10-02 13:57 ` Martin Ertsås
2012-10-02 14:02 ` Otavio Salvador
2012-10-02 13:50 ` Phil Blundell
2013-04-25 11:12 ` Phil Blundell
2013-04-25 11:21 ` Martin Jansa
2013-04-25 13:47 ` Mark Hatle
2013-04-26 13:57 ` Phil Blundell
2013-04-26 14:16 ` Mark Hatle
2013-04-26 14:27 ` Phil Blundell
2013-04-26 14:39 ` Mark Hatle
2013-04-26 14:41 ` Phil Blundell
2013-04-26 14:50 ` Otavio Salvador
2013-04-26 16:05 ` Mark Hatle
2013-04-27 21:15 ` Chris Larson
2013-04-29 20:10 ` Debug Packaging (was: rootfs_ipk, image: Add debug capture support) Richard Purdie
2013-04-30 10:45 ` Phil Blundell
2013-04-30 15:24 ` Debug Packaging Mark Hatle
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=506AF195.9040008@cisco.com \
--to=mertsas@cisco.com \
--cc=openembedded-core@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.