From: Mihai Moldovan <ionic@ionic.de>
To: Vadim Kochan <vadim4j@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] ss: Fix wrong filter behaviour
Date: Thu, 30 Apr 2015 14:13:13 +0200 [thread overview]
Message-ID: <55421C59.9040303@ionic.de> (raw)
In-Reply-To: <20150430072655.GA689@angus-think.wlc.globallogic.com>
[-- Attachment #1: Type: text/plain, Size: 383 bytes --]
On 30.04.2015 09:26 AM, Vadim Kochan wrote:
> I think it depends on distro package maintainers, usually they track the
> upstream fixes and uses them in their stable versions, may be I should
> grep some maintainers emails (LARTC mailing list ?) and broadcast to them ?
Well... that's strictly speaking not your responsibility. I can make them aware,
I guess?
Mihai
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next prev parent reply other threads:[~2015-04-30 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1430227008-7440-1-git-send-email-vadim4j@gmail.com>
[not found] ` <20150428133745.GA10292@angus-think.wlc.globallogic.com>
2015-04-29 21:22 ` [PATCH] ss: Fix wrong filter behaviour Mihai Moldovan
2015-04-30 7:26 ` Vadim Kochan
2015-04-30 12:13 ` Mihai Moldovan [this message]
2015-04-30 16:19 ` Stephen Hemminger
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=55421C59.9040303@ionic.de \
--to=ionic@ionic.de \
--cc=netdev@vger.kernel.org \
--cc=vadim4j@gmail.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).