From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/1] package/avahi: bump version to 0.7
Date: Mon, 27 Nov 2017 09:37:46 +0100 [thread overview]
Message-ID: <20171127093746.182aca43@windsurf.lan> (raw)
In-Reply-To: <20171125161031.24150-1-bernd.kuhls@t-online.de>
Hello,
On Sat, 25 Nov 2017 17:10:31 +0100, Bernd Kuhls wrote:
> Added license hash, removed license text in avahi.mk added in 2006:
> https://git.buildroot.net/buildroot/commit/package/avahi?id=21e97d3e155f4d9604f729698cdfff3c40eefbe7
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/avahi/avahi.hash | 3 ++-
> package/avahi/avahi.mk | 9 +--------
> 2 files changed, 3 insertions(+), 9 deletions(-)
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-11-27 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 16:10 [Buildroot] [PATCH/next 1/1] package/avahi: bump version to 0.7 Bernd Kuhls
2017-11-27 8:37 ` Thomas Petazzoni [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=20171127093746.182aca43@windsurf.lan \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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