From: Alejandro del Castillo <alejandro.delcastillo@ni.com>
To: Haris Okanovic <haris.okanovic@ni.com>, <yocto@yoctoproject.org>
Cc: Ken Sharp <ken.sharp@ni.com>
Subject: Re: [PATCH] opkg-utils: Add opkg-graph-deps
Date: Wed, 6 Jan 2016 18:01:37 -0600 [thread overview]
Message-ID: <568DAAE1.8020901@ni.com> (raw)
In-Reply-To: <1451951145-10297-1-git-send-email-haris.okanovic@ni.com>
On 01/04/2016 05:45 PM, Haris Okanovic wrote:
> Usage: opkg-graph-deps [-h] [-o feed.dot] [-u <base feed URL>] <paths to
> Packages>
>
> Generates a dot formatted dependency graph of an IPK feed.
>
> The feed is specified by a list of IPK index (Packages) files, which
> are sourced in the order specified to build a dependency graph. Last
> index to declare a package wins, but also generates a warning to stderr.
>
opkg-utils development happens on opkg-devel@googlegroups.com. Can you resend?
(you also don't need to CC Paul anymore)
Thanks for the work on this, look like a great addition to opkg-utils.
--
Cheers,
Alejandro
prev parent reply other threads:[~2016-01-07 0:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 23:45 [PATCH] opkg-utils: Add opkg-graph-deps Haris Okanovic
2016-01-07 0:01 ` Alejandro del Castillo [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=568DAAE1.8020901@ni.com \
--to=alejandro.delcastillo@ni.com \
--cc=haris.okanovic@ni.com \
--cc=ken.sharp@ni.com \
--cc=yocto@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.