From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/Config.in: move libvpx to Libraries/Multimedia
Date: Mon, 2 Nov 2015 16:16:37 +0100 [thread overview]
Message-ID: <20151102161637.1ee2a1f2@free-electrons.com> (raw)
In-Reply-To: <20151101173326.GJ3352@tarshish>
Baruch,
On Sun, 1 Nov 2015 19:33:26 +0200, Baruch Siach wrote:
> Hi Bernd,
>
> On Sun, Nov 01, 2015 at 06:30:04PM +0100, Bernd Kuhls wrote:
> > Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
>
> A short explanation why this move makes sense would be nice.
I agree. In this specific case, it is relatively obvious IMO, but in
general, more verbose commit messages are always good.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-11-02 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 17:30 [Buildroot] [PATCH 1/1] package/Config.in: move libvpx to Libraries/Multimedia Bernd Kuhls
2015-11-01 17:33 ` Baruch Siach
2015-11-02 15:16 ` Thomas Petazzoni [this message]
2015-11-02 15:16 ` Thomas Petazzoni
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=20151102161637.1ee2a1f2@free-electrons.com \
--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