From: Jamal Hadi Salim <jhs@mojatatu.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Anton 'EvilMan' Danilov <littlesmilingcloud@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] pedit action: add mask for changing bits.
Date: Thu, 26 Apr 2012 06:21:36 -0400 [thread overview]
Message-ID: <1335435696.7123.1.camel@mojatatu> (raw)
In-Reply-To: <20120425131532.79ad7e6b@nehalam.linuxnetplumber.net>
On Wed, 2012-04-25 at 13:15 -0700, Stephen Hemminger wrote:
> Did you come to a conclusion, should it be applied as is?
No, dont apply it as is please.
EvilMan should have a new version when he gets to it.
cheers,
jamal
prev parent reply other threads:[~2012-04-26 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-25 18:01 [PATCH iproute2] pedit action: add mask for changing bits Anton 'EvilMan' Danilov
2012-02-27 13:58 ` jamal
2012-02-27 14:15 ` Anton 'EvilMan' Danilov
2012-02-28 13:05 ` Jamal Hadi Salim
2012-02-29 13:12 ` Anton 'EvilMan' Danilov
2012-02-29 14:01 ` jamal
2012-04-25 20:15 ` Stephen Hemminger
2012-04-26 10:21 ` Jamal Hadi Salim [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=1335435696.7123.1.camel@mojatatu \
--to=jhs@mojatatu.com \
--cc=littlesmilingcloud@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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;
as well as URLs for NNTP newsgroup(s).