netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: ipt_LOG: No space after prefix
Date: Sun, 22 Jan 2012 15:26:05 +0100	[thread overview]
Message-ID: <4F1C1C7D.7040200@nod.at> (raw)
In-Reply-To: <alpine.LNX.2.01.1201221519200.10337@frira.zrqbmnf.qr>

[-- Attachment #1: Type: text/plain, Size: 260 bytes --]

Am 22.01.2012 15:20, schrieb Jan Engelhardt:
> Changing it now will break log analyzers as well. So you are better off 
> leaving it as-is, because everybody who has observed that before you 
> already knows about it.

Very true.

Thanks,
//richard


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

      reply	other threads:[~2012-01-22 14:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-22 12:54 ipt_LOG: No space after prefix Richard Weinberger
2012-01-22 14:20 ` Jan Engelhardt
2012-01-22 14:26   ` Richard Weinberger [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=4F1C1C7D.7040200@nod.at \
    --to=richard@nod.at \
    --cc=jengelh@medozas.de \
    --cc=netdev@vger.kernel.org \
    --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).