From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH] Incrementing dnsmasq version to address a bug with libvirt and DHCP.
Date: Tue, 08 Apr 2014 14:24:32 +0200 [thread overview]
Message-ID: <li0ppv$tv0$1@ger.gmane.org> (raw)
In-Reply-To: <1396957806-7835-1-git-send-email-Christian.Ziethen@enea.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Christian Ziethén schreef op 08-04-14 13:50:
> Subject: Incrementing dnsmasq version to address a bug with libvirt and
> DHCP.
The OE styleguide says the commit summary should look like this:
dnsmasq: update to 2.68 to fix a bug with libvirt and DHCP
And if would be nice if you can state what that bug was in the commit log.
>
> Signed-off-by: Christian Ziethén <Christian.Ziethen@enea.com> ---
> meta-networking/recipes-support/dnsmasq/dnsmasq_2.63.bb | 4 ----
> meta-networking/recipes-support/dnsmasq/dnsmasq_2.68.bb | 4 ++++ 2
> files changed, 4 insertions(+), 4 deletions(-) delete mode 100644
> meta-networking/recipes-support/dnsmasq/dnsmasq_2.63.bb create mode
> 100644 meta-networking/recipes-support/dnsmasq/dnsmasq_2.68.bb
>
> diff --git a/meta-networking/recipes-support/dnsmasq/dnsmasq_2.63.bb
> b/meta-networking/recipes-support/dnsmasq/dnsmasq_2.63.bb deleted file
> mode 100644 index 2df3713..0000000 ---
> a/meta-networking/recipes-support/dnsmasq/dnsmasq_2.63.bb +++ /dev/null
> @@ -1,4 +0,0 @@ -require dnsmasq.inc - -SRC_URI[dnsmasq-2.63.md5sum] =
> "43e771997615ebcd8f6c6ffa60c3e40b" -SRC_URI[dnsmasq-2.63.sha256sum] =
> "fd86e3bcc6a63c76e35e4a20baa790e7bbbfc7b43845cae85ca8ffd024467710" diff
> --git a/meta-networking/recipes-support/dnsmasq/dnsmasq_2.68.bb
> b/meta-networking/recipes-support/dnsmasq/dnsmasq_2.68.bb new file mode
> 100644 index 0000000..651c304 --- /dev/null +++
> b/meta-networking/recipes-support/dnsmasq/dnsmasq_2.68.bb @@ -0,0 +1,4
> @@ +require dnsmasq.inc + +SRC_URI[dnsmasq-2.63.md5sum] =
> "6f8351ca0901f248efdb81532778d2ef" +SRC_URI[dnsmasq-2.63.sha256sum] =
> "402019d61f53f1ccc04cc6218719fd3b158ea3fca9a83ab55471f981a2097c2f"
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFTQ+p/MkyGM64RGpERApogAJ0dFnpj5z5+j173AaYJUWDtDYC1TQCgiVNX
cpQyNpJHFEcv6uqeHfCymuc=
=PnyA
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2014-04-08 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 11:50 [meta-networking][PATCH] Incrementing dnsmasq version to address a bug with libvirt and DHCP Christian Ziethén
2014-04-08 12:24 ` Koen Kooi [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='li0ppv$tv0$1@ger.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.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