From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] minidlna: bump version to 1.1.1
Date: Thu, 2 Jan 2014 10:00:53 +0100 [thread overview]
Message-ID: <20140102100053.36532f4d@skate> (raw)
In-Reply-To: <BLU0-SMTP1245369C4049BDF785E78C9D9C80@phx.gbl>
Dear Bernd Kuhls,
On Wed, 1 Jan 2014 21:42:49 +0100, Bernd Kuhls wrote:
>
> Signed-off-by: Bernd Kuhls <berndkuhls@hotmail.com>
> ---
> .../minidlna-0001-fix-genconfig-script.patch | 95 --------------------
> package/minidlna/minidlna-0002-fix-Makefile.patch | 20 -----
> .../minidlna-0003-fix-missing-include.patch | 19 ----
> .../minidlna-0004-fix-libavformat-use.patch | 20 -----
> package/minidlna/minidlna.mk | 45 +---------
> 5 files changed, 4 insertions(+), 195 deletions(-)
> delete mode 100644 package/minidlna/minidlna-0001-fix-genconfig-script.patch
> delete mode 100644 package/minidlna/minidlna-0002-fix-Makefile.patch
> delete mode 100644 package/minidlna/minidlna-0003-fix-missing-include.patch
> delete mode 100644 package/minidlna/minidlna-0004-fix-libavformat-use.patch
Thanks, but for such massive changes made to bump a package, please
write a more detailed commit log that details:
* Why some patches are removed.
* What are the different changes in the .mk file made for.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-01-02 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-01 20:42 [Buildroot] [PATCH 1/1] minidlna: bump version to 1.1.1 Bernd Kuhls
2014-01-02 9:00 ` 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=20140102100053.36532f4d@skate \
--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