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: [PATCH] dnsmasq: 2.76test10 with latest patches (001-004)
Date: Fri, 04 Mar 2016 12:00:39 +0000	[thread overview]
Message-ID: <1457092839.6973.37.camel@ipfire.org> (raw)
In-Reply-To: <H000006e001f5c44.1457031971.mail.at4b.net@MHS>

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

Hi,

it is indeed a question of testing.

We intend to release it soon, but unfortunately there is only little
man power to work on an other architecture. So contribution is
appreciated.

Best,
-Michael

On Thu, 2016-03-03 at 14:06 -0500, Kienker, Fred wrote:
> Is there any chance the x86_64 version will ever be released? If it
> is a 
> question of testing, I will volunteer to test it.
> 
> Best regards,
> Fred Kienker
> 
> -----Original Message-----
> From: Michael Tremer [mailto:michael.tremer(a)ipfire.org] 
> Sent: Wednesday, March 02, 2016 6:49 PM
> To: Paul Simmons; development(a)lists.ipfire.org
> Subject: Re: [PATCH] dnsmasq: 2.76test10 with latest patches (001-
> 004)
> 
> Hi,
> 
> On Mon, 2016-02-29 at 15:39 -0600, Paul Simmons wrote:
> > On Mon, 2016-02-29 at 20:22 +0100, Matthias Fischer wrote:
> > > Hi,
> > > 
> > > On 28.02.2016 21:19, Michael Tremer wrote:
> > > > 
> > > > I merged this patch and the one after.
> > > > 
> > > > Please give this version a good test as it is a pre-release 
> > > > version.
> > > Its running here.
> > > 
> > > > 
> > > > You can maintain a branch where you integrate all new changes,
> > > > but 
> 
> > > > I think it is not required to send every single one to the
> > > > mailing 
> 
> > > > list.
> > > > It creates a bit of noise and I think that unfortunately nobody
> > > > is 
> 
> > > > testing every single one any ways. Which is sad.
> > > Yep. ;-)
> > > 
> > > > 
> > > > Can we have maybe one aggregated patch after every release of
> > > > a 
> > > > Core Update? So we always have the latest version of dnsmasq
> > > > in 
> > > > the updates?
> > > I'll do that. If not otherwise wanted, I'll send the current - 
> > > patched - version after every Core Update.
> > > 
> > > Best,
> > > Matthias
> > 
> > @list:
> > 
> > I hope to have an opportunity to test RealSoonNow via an alternate 
> > boot scheme on current hardware.
> > 
> > Do you want me to test the i586 or the x86_64?
> 
> Ideally both :) But as we do not release the 64 bit builds at the 
> moment, i586 is preferred.
> 
> Best,
> -Michael
> 
> > 
> > Paul
> 

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

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2016-02-26 17:45 Matthias Fischer
  -- 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=1457092839.6973.37.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