From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: With new Patches 030-041 'dnsmasq' 2.75 won't compile anymore
Date: Wed, 06 Jan 2016 20:55:03 +0100 [thread overview]
Message-ID: <568D7117.8010907@ipfire.org> (raw)
In-Reply-To: <1452108714.31655.304.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
Hi,
On 06.01.2016 20:31, Michael Tremer wrote:
> I do read the list. Simon uploaded a patch so that it builds.
Just saw it - and the "Devel" is running with patches 001-042 right now.
> I am not sure though if we should have a testing version like that in
> the distribution at this stage. Is there a chance that it will become
> stable until C97 will be released?
I'm with you in this point => *I* wouldn't want such 'testing' version in
*my* distribution. I would do this only if there is *really* no other
way.
Will it be stable? I hope so. The problem is, I *don't have problems*...
None of the 'dnsmasq'-crashes I heard of ever happened here.
> I see what issue you are trying to tackle here, but Simon considers
> this code as a bit wonkey (from what I saw in the commit messages). Can
> you maybe consult with him?
You mean the 'dhcp_lease_new'-warning while compiling 'isc.c'? ;-)
I'll ask about it when the new patched version is ready and the problem
still persists (which I fear will be the case...).
Best,
Matthias
prev parent reply other threads:[~2016-01-06 19:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 11:55 Matthias Fischer
2016-01-04 16:42 ` Michael Tremer
2016-01-04 19:04 ` Matthias Fischer
2016-01-04 22:59 ` Matthias Fischer
2016-01-04 23:00 ` Michael Tremer
2016-01-04 23:30 ` Matthias Fischer
2016-01-05 19:53 ` Matthias Fischer
2016-01-06 19:31 ` Michael Tremer
2016-01-06 19:55 ` 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=568D7117.8010907@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