From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: dnsmasq_276test10_2016-02-27
Date: Sat, 05 Mar 2016 10:15:31 +0100 [thread overview]
Message-ID: <56DAA3B3.5040501@ipfire.org> (raw)
In-Reply-To: <H000006e001f5b50.1457031836.mail.at4b.net@MHS>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
Hi,
On 03.03.2016 20:03, 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.
Sounds good. ;-)
> A big thanks to Matthias Fishcer for all of his hard work keeping up
> with the never ending stream of patches to dnsmasq.
No problem, thanks.
Just for the records and for testers:
I've stopped commiting and pushing *every* single patch to GIT, since it
produces too much noise on both.
The next "official, stable" - as Michael wrote: "aggregated patch",
based on 'next' - will be published after the next core update.
In the meantime, I'll try to keep the dnsmasq-releases as current as
possible. To make downloads a bit easier, I changed the download
directory! I've moved all 'dnsmasq'-version to
http://people.ipfire.org/~mfischer/dnsmasq/...
Latest version from tonight is 'dnsmasq_276test12_2016-03-05'. It
contains ALL previous patches - plus patch '001' from
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=d1377fa3c4f6093611dee8d610f6953eb8145d21
- and is running here without seen problems so far.
Best,
Matthias
prev parent reply other threads:[~2016-03-05 9:15 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 ` dnsmasq_276test10_2016-02-27 Michael Tremer
2016-03-05 9:15 ` Matthias Fischer [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=56DAA3B3.5040501@ipfire.org \
--to=matthias.fischer@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