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 for mtr, fping, lynis and nmap updates
Date: Wed, 28 Jan 2015 22:56:08 +0100	[thread overview]
Message-ID: <1422482168.23522.0.camel@ipfire.org> (raw)
In-Reply-To: <A5CCE447-ACF5-4114-B5E1-FAA0FAB873A6@ipfire.org>

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

Hi,

I merged them all. Some into master, some into next. That got noted in
all the individual bug reports.

Thanks for sending this in and apologies for the delay.

-Michael

On Tue, 2015-01-13 at 16:48 +0100, Skalarwelle wrote:
> Hi all,
> i wanted to introduce updates for 
> 
> 
> mtr —> https://bugzilla.ipfire.org/show_bug.cgi?id=10717
> fping —> https://bugzilla.ipfire.org/show_bug.cgi?id=10718
> lynis —> https://bugzilla.ipfire.org/show_bug.cgi?id=10715
> and
> nmap —> https://bugzilla.ipfire.org/show_bug.cgi?id=10716
> 
> 
> Greetings,
> 
> 
> Erik
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development



           reply	other threads:[~2015-01-28 21:56 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <A5CCE447-ACF5-4114-B5E1-FAA0FAB873A6@ipfire.org>]

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=1422482168.23522.0.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