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: dnsmasq_276test10_2016-02-27
Date: Fri, 04 Mar 2016 12:20:30 +0000	[thread overview]
Message-ID: <1457094030.6973.52.camel@ipfire.org> (raw)
In-Reply-To: <H000006e001f5b50.1457031836.mail.at4b.net@MHS>

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

Hi,

who is "we"? How many installations are this?

Best,
-Michael

On Thu, 2016-03-03 at 14:03 -0500, Kienker, Fred wrote:
> I’m happy to report the dnsmasq_276test10_2016-02-27 version has been
> very solid in testing and we have released it to our production
> systems where it continues to be very stable with no issues what so
> ever so far. A big thanks to Matthias Fishcer for all of his hard
> work keeping up with the never ending stream of patches to dnsmasq.
> Best regards,
> Fred Kienker

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

       reply	other threads:[~2016-03-04 12:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <H000006e001f5b50.1457031836.mail.at4b.net@MHS>
2016-03-04 12:20 ` Michael Tremer [this message]
2016-03-05  9:15 ` dnsmasq_276test10_2016-02-27 Matthias Fischer

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