From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Daniel Drake <dsd@gentoo.org>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH iptables] libxt_output: add more spaces to output
Date: Mon, 19 Jan 2009 15:37:19 +0100 [thread overview]
Message-ID: <4974901F.6000002@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0901171431250.2904@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Saturday 2009-01-17 14:14, Daniel Drake wrote:
>
>> Commit bb9284d1 ("libxt_owner: add spaces to output") moved the printing
>> of spaces away from the owner_mt_print() function family, but forgot to
>> add spaces in all of the print_item() functions that are called.
>>
>> This is likely to be at least the partial cause of
>> https://bugs.gentoo.org/show_bug.cgi?id=254435
>
> Approves-of-this-patch: Jan Engelhardt <jengelh@medozas.de>
Applied, thanks.
prev parent reply other threads:[~2009-01-19 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090117131414.66A2F9D4077@zog.reactivated.net>
2009-01-17 13:33 ` [PATCH iptables] libxt_output: add more spaces to output Jan Engelhardt
2009-01-19 14:37 ` 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=4974901F.6000002@trash.net \
--to=kaber@trash.net \
--cc=dsd@gentoo.org \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.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).