From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: New addon monit
Date: Mon, 11 Aug 2014 11:10:44 +0200 [thread overview]
Message-ID: <1407748244.2114.14.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <b96819fcd6654ec48e2bd825a81529ce@mx6-sysproserver.de>
[-- Attachment #1: Type: text/plain, Size: 853 bytes --]
Hi Dirk,
I was going to merge this. Unfortunately, there is lots of asterisk
stuff in it which has not been merged yet.
So You can either create a clean branch based on "next" and cherry-pick
all commits related to monit or we can wait until asterisk is merged.
That requires that there have been no rebases on that branch.
-Michael
On Mon, 2014-07-28 at 09:30 +0200, Dirk Wagner wrote:
> Hi,
>
> I created a new addon monit http://mmonit.com/monit/
>
> Here is a nice presentation what monit can do for you:
> http://slides.com/tildeslash/monit#/
>
> Plz pull from:
> http://git.ipfire.org/?p=people/glotzi/ipfire-2.x.git;a=shortlog;h=refs/heads/monit
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
prev parent reply other threads:[~2014-08-11 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 7:30 Dirk Wagner
2014-08-11 9:10 ` 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=1407748244.2114.14.camel@rice-oxley.tremer.info \
--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