From: Joe MacDonald <Joe.MacDonald@windriver.com>
To: Aws Ismail <aws.ismail@windriver.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH 0/2][V3] Quagga: deal with snmp support, and some cleanup.
Date: Tue, 26 Mar 2013 15:56:08 -0400 [thread overview]
Message-ID: <20130326195604.GA3692@windriver.com> (raw)
In-Reply-To: <1364225407-13263-1-git-send-email-aws.ismail@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 947 bytes --]
[[meta-networking][PATCH 0/2][V3] Quagga: deal with snmp support, and some cleanup.] On 13.03.25 (Mon 11:30) Aws Ismail wrote:
>
> *** V3 ***
> Cleanup whitespaces and hardtabs
> This is made a separate new commit
> *** V3 ***
>
> Overall, this commit introduces a set of changes to do the following:
>
> 1. Update the configure option for quagga to replace the old --enable-tcp-md5
> 2. Add snmp support based on DISTRO_FEATURES availability.
> 3. Install sample runtime configuration files for quagga and its daemons.
> 4. Make sure the post install script is executed at the right stage.
>
> Aws Ismail (2):
> Quagga has no snmp support, unrecognized options --enable-tcp-md5
> Quagga: clean up whitespaces/hardtabs in recipe
>
> .../recipes-protocols/quagga/quagga.inc | 71 ++++++++++++--------
> 1 files changed, 43 insertions(+), 28 deletions(-)
Merged, thanks.
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2013-03-26 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 15:30 [meta-networking][PATCH 0/2][V3] Quagga: deal with snmp support, and some cleanup Aws Ismail
2013-03-25 15:30 ` [meta-networking][PATCH 1/2] Quagga has no snmp support, unrecognized options --enable-tcp-md5 Aws Ismail
2013-03-25 15:30 ` [meta-networking][PATCH 2/2] Quagga: clean up whitespaces/hardtabs in recipe Aws Ismail
2013-03-26 19:56 ` Joe MacDonald [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=20130326195604.GA3692@windriver.com \
--to=joe.macdonald@windriver.com \
--cc=aws.ismail@windriver.com \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox