From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] bind: Update to 9.9.5
Date: Sun, 09 Mar 2014 23:09:52 -0700 [thread overview]
Message-ID: <1394431792.7883.51.camel@ted> (raw)
In-Reply-To: <1394423288-11049-4-git-send-email-sgw@linux.intel.com>
On Sun, 2014-03-09 at 20:48 -0700, Saul Wold wrote:
> Remove CVE patches that are in bind
> Updated COPYRIGHT includes date changes the NetBSD Copyright
> Modifies the Base BSD License to 3-Clause (removes advertising clause)w
> Add patch to disable running tests on host
> bind: Add python-core for dnssec
>
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
Judging from the autobuilder failures, this one could still use some
work :/
Cheers,
Richard
next prev parent reply other threads:[~2014-03-10 6:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 3:48 [PATCH 0/3] Package Updates Saul Wold
2014-03-10 3:48 ` [PATCH 1/3] util-linux: Update to 2.24.1 Saul Wold
2014-03-10 3:48 ` [PATCH 2/3] dhcp: Update to 4.3.0 Saul Wold
2014-03-10 3:48 ` [PATCH 3/3] bind: Update to 9.9.5 Saul Wold
2014-03-10 6:09 ` Richard Purdie [this message]
2014-03-10 14:12 ` Saul Wold
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=1394431792.7883.51.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/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