From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Rsyslog: New advanced syslogger [TESTING]
Date: Wed, 14 Feb 2018 20:29:59 +0000 [thread overview]
Message-ID: <1518640199.15001.16.camel@ipfire.org> (raw)
In-Reply-To: <1518617836.3543.55.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]
On Wed, 2018-02-14 at 15:17 +0100, ummeegge wrote:
> Hi Michael,
>
> Am Mittwoch, den 14.02.2018, 11:52 +0000 schrieb Michael Tremer:
> > Hi,
> >
> > I am in favour of this too, but my schedule is really busy at the
> > moment and
> > would not like to get involved into any new projects. We have loads
> > of stuff on
> > the list anyways like OpenVPN, OpenSSL, new kernel, etc.
>
> Sure.
>
> >
> > So I would be happy if you would work on this.
>
> I can do this but let us finish the openssl-11 thing first.
>
> > Please include Peter since he
> > proposed this in the first place and wanted the TCP logging
> > capability.
>
> This was my intend to send all that to the mailinglist. Should i write
> him an email ?
Please keep in the open what can be done in the open.
Make sure that he is CCed, is involved in testing so that the right git tags are
being set: https://wiki.ipfire.org/devel/git/tags
>
> >
> > But I think we should prioritise OpenVPN first which is way more
> > urgent than
> > replacing the syslog daemon.
>
> Exactly
>
>
> Greetings,
>
> Erik
next prev parent reply other threads:[~2018-02-14 20:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 8:56 Erik Kapfer
2018-02-06 9:14 ` ummeegge
2018-02-13 6:26 ` ummeegge
2018-02-13 10:09 ` Michael Tremer
2018-02-13 12:41 ` ummeegge
2018-02-14 11:52 ` Michael Tremer
2018-02-14 14:17 ` ummeegge
2018-02-14 20:29 ` Michael Tremer [this message]
2018-02-27 12:38 ` ummeegge
[not found] <1517906901-30146-1-git-send-email-erik.kapfer@ipfire.org>
2018-04-08 17:47 ` ummeegge
2018-04-09 17:43 ` Peter Müller
2018-04-10 9:29 ` ummeegge
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=1518640199.15001.16.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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