public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [Merge Request] Guardian 2.0
Date: Tue, 02 Aug 2016 14:49:05 +0100	[thread overview]
Message-ID: <1470145745.2710.422.camel@ipfire.org> (raw)
In-Reply-To: <1470077630.5573.9.camel@ipfire.org>

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

Thank you very much. I merged this one with a small number of additional fixes.

I also created so bug reports about minor bugs which is mainly UI related and is
not a deal-breaker for this release, but I think should generally be resolved.

A testing release should be available shortly, so that a larger number of
testers can join testing Guardian.

Best,
-Michael

On Mon, 2016-08-01 at 20:53 +0200, Stefan Schantl wrote:
> Hello,
> 
> this is the merge request to include guardian 2.0 into IPFire 2.x.
> 
> All changes are stored at the "guardian-2.0" branch in my personal
> IPFire-2.x repository.
> 
> http://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=shortlog;h=refs
> /heads/guardian-2.0
> 
> A short summary of the containing changes:
> 
> * Update guardian to the newly developed "guardian 2.0".
> 	- Add backup file for this service.
> 	- Add logrotate file.
> 	- Add initscript.
> 	- Remove old guardian code.
> 
> * Add "guardian.cgi" to administrate guardian.
> 
> * Remove guardian related code from "ids.cgi" and "snort" initscript.
> (shipped by the core update)
> 
> * Add required language strings to the english and german language
> files. (core update)
> 
> Please have a look at my changes and if everything is okay merge them
> into the next branch to get them released / shipped by the next core
> update (core 104).
> 
> Thanks in advance,
> 
> -Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2016-08-02 13:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01 18:53 Stefan Schantl
2016-08-02 13:49 ` Michael Tremer [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=1470145745.2710.422.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