From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] dnsmasq: 2.76test10 with latest patches (001-004)
Date: Fri, 26 Feb 2016 18:45:32 +0100 [thread overview]
Message-ID: <56D08F3C.6010406@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 282 bytes --]
Hi,
For explanation - I hope I didn't garble anything...
Thinking it over, I decided to create a new diff-patch for '2.75' =>
'2.76test10', completely based on current 'next' - containing the latest
patches.
This version was tested here and is running right now.
Best,
Matthias
next reply other threads:[~2016-02-26 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 17:45 Matthias Fischer [this message]
[not found] <1456781959.3052.8.camel@hughes.net>
2016-03-02 23:49 ` Michael Tremer
2016-03-03 19:06 ` Kienker, Fred
2016-03-04 12:00 ` Michael Tremer
-- strict thread matches above, loose matches on Subject: below --
2016-02-26 17:29 Matthias Fischer
2016-02-28 20:19 ` Michael Tremer
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=56D08F3C.6010406@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