From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Core Team <netfilter-devel@vger.kernel.org>,
Eric Leblond <eric@regit.org>
Subject: Re: [PATCH] pgsql: add SSL connection implementation to PGSQL plugin
Date: Mon, 03 Sep 2012 02:38:35 +0100 [thread overview]
Message-ID: <50440A1B.7060908@googlemail.com> (raw)
In-Reply-To: <20120902233228.GA22069@1984>
> I won't take a patch that fixes a NULL pointer dereference and adds a
> new feature.
>
> Please, split this in two patches. First fix the bug, then add the new
> fature.
Sure. Are there any (other) objections to the patch I submitted?
next prev parent reply other threads:[~2012-09-03 1:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-01 12:51 [PATCH] pgsql: add SSL connection implementation to PGSQL plugin Mr Dash Four
2012-09-02 15:49 ` Eric Leblond
2012-09-02 16:24 ` Mr Dash Four
2012-09-02 23:32 ` Pablo Neira Ayuso
2012-09-03 1:38 ` Mr Dash Four [this message]
2012-09-03 6:33 ` Eric Leblond
2012-09-03 12:00 ` Mr Dash Four
2012-11-07 8:41 ` Eric Leblond
2012-11-10 23:17 ` Mr Dash Four
2012-09-18 19:28 ` Pablo Neira Ayuso
2012-09-20 22:33 ` Mr Dash Four
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=50440A1B.7060908@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=eric@regit.org \
--cc=netfilter-devel@vger.kernel.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 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).