From: Patrick McHardy <kaber@trash.net>
To: Alan Ezust <alan.ezust@presinet.com>
Cc: netfilter-devel@lists.netfilter.org, pablo@netfilter.org
Subject: Re: [PATCH 1/2]: conntrack: fix refcount leak when findingexpectation
Date: Tue, 28 Nov 2006 14:14:08 +0100 [thread overview]
Message-ID: <456C3620.9080209@trash.net> (raw)
In-Reply-To: <200611271132.21563.alan.ezust@presinet.com>
Alan Ezust wrote:
> I noticed many messages indicating that things are being applied to conntrack
> and their related libs - but whenever I check my own checked out copy from
> svn (rev 6698), it does not show me anything new to update, and it appears as
> if nobody is committing to that particular part of the repo. Are you
> committing these changes to a branch other than trunk?
This patch was against the kernel not the libraries. The others you
mention probably as well.
prev parent reply other threads:[~2006-11-28 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200611232315.kANNFVi3006773@toshiba.co.jp>
2006-11-27 17:32 ` [PATCH 1/2]: conntrack: fix refcount leak when finding expectation Patrick McHardy
2006-11-27 19:32 ` [PATCH 1/2]: conntrack: fix refcount leak when findingexpectation Alan Ezust
2006-11-28 13:14 ` Patrick McHardy [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=456C3620.9080209@trash.net \
--to=kaber@trash.net \
--cc=alan.ezust@presinet.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@netfilter.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.